[Kde-accessibility] Dependency between kdeaccessibility and kdemultimedia?

Gary Cramblitt garycramblitt at comcast.net
Fri Dec 17 20:09:06 CET 2004


On Friday 17 December 2004 01:54 pm, Olaf Schmidt wrote:
> [Gary Cramblitt, Freitag, 17. Dezember 2004 19:28]
>
> > KTTSD has a dependency on gstreamer, which we put into a separate
> > package (kttsd-gstreamer).  Maybe we should combine this with ksayit FX
> > plugin and distribute kdeaccessibility-extras?
>
> The problem is that we don't know how the packegers will split up the
> kdeaccessibility tarballs we provide. And having a dependency on
> kdemultimedia changes the build order, even if the packagers decide to
> split the kdemultimedia dependent part into an extra package.
>
> The cleanest solution would be to have both plug-ins somewhere else in
> CVS, for example kdeextragear.

The kttsd gstreamer plugin is already conditionally compiled and if plugin is 
not available at runtime, is not a problem.  But I do need to add a configure 
option (--enable-kttsd-gstreamer) that should probably default to false.

Splitting out kttsd gstreamer into yet another module doesn't appeal to me 
much; KTTS is already fragmented quite a bit already.  Besides, the kttsd 
gstreamer plugin is dependent upon libkttsd, so if it were moved to 
kdeextreager, there would be a dependency between kdeextragear and 
kdeaccessibility.  I don't think Debian packagers will have a problem, but I 
can't speak for RPM and gentoo packagers.  If it comes down to moving kttsd 
gstreamer into kdeextragear, I'd opt to remove it altogether; GStreamer has 
some issues.

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


More information about the kde-accessibility mailing list