[Pkg-kde-talk] [cross reading needed] kdeaccessibility ...

[Gary Cramblitt]

On Thursday 03 March 2005 01:28 pm, Pierre Habouzit wrote:
> [kttsd bloat]
>
> I've not less than 5 packages for kttsd :
>
>   kttsd
>   kttsd-(epos|flite|festival)-syntplugin
>   kttsd-nonfree-plugins
>
> There is a README.Debian in kttsd, that explains the situation in [1]
>
> The split has been made because the plugins roughly system/exec some
> epos/flite/festival binaries.
> I've not tested if the lack of epos/flite/festival will make them
> segfault or no. But I fear users questions about them not working. So i
> prefer having them in separate packages, with dependencies on
> epos/flite/festival consequently.
>
> [1] http://tinyurl.com/5pcav

I don't think it is necessary to split the epos|flite|festival|freetts plugins 
into separate packages.  When user configures kttsd, the plugins detect if 
the corresponding executables are available, and if not, disables that 
functionality.  In other words, user cannot configure that plugin.  This will 
be obvious to the user because each plugin asks for the path to the 
executable.  It will be less confusing for users to go ahead and include them 
in the kdeaccessibility package.  Also, users may wish to install the synth 
binaries after installing kdeaccessibility, in which case, kttsd will 
automatically adapt.

I'm also concerned how kttsd will behave if there are no synth plugins 
available at all.  I don't think that code path has ever been tested. :/

>   kttsd-nonfree-plugins

Since the synth plugins are runtime only dependent on the synths, I don't see 
why non-free licences for the synths are an issue, but then I am not a debian 
packager.

-- 
Gary Cramblitt (aka PhantomsDad)
KDE Text-to-Speech Maintainer
http://accessibility.kde.org/developer/kttsd/index.php