On Sun, 17 Jun 2001, Alexander Skwar wrote:
>
> > (or just leave out libgmcop.*) or put it in a 'libarts-glib'
> > package if there is going to be any package using that library
>
> Even if there's no package in Cooker, there may be some other program out
> there which depends on libgmcop, so the best sollution IMHO would be, to
> create a libarts-glib and maybe also libarts-glib-devel package.
>
Yes, it would definitely be cleaner, but on the other hand it would
require rebuilding and distributing all of kdelibs whenever a new version
of glib comes out just for the sake of satisfying a dependency that noone
cares about.
libgmcop is just a few months old, is part of an alpha
release of kde, depends on the unstable release of glib and the
only application that seems to be using it (gnome-arts) requires
a newer version of arts (0.5.4) than the one shipping with KDE.
I think it sould be safe to wait with inclusion until there is need
for it.
Probably either way is ok, but the current situation is not.
Arnd <><
links:
http://www.arts-project.org/doc/gnome-arts-0.1.2.html
http://space.twc.de/~stefan/kde/arts-mcop-doc/NEWS
