glib dependancy in KDE3.x

Stefan Westerfeld stefan at
Thu Mar 6 10:02:24 GMT 2003


On Thu, Mar 06, 2003 at 01:32:57AM -0800, Neil Stevens wrote:
> On Thursday March 06, 2003 01:03, Stefan Westerfeld wrote:
> > Thus, I am considering removing the glib compatibility code from aRts,
> > and depending on the real thing in the future. The question is: are
> > there any objections and/or comments against doing this within the
> > KDE3.x cycle (i.e. for KDE3.2)?
> The glib stuff is entirely internal to artsd right?

I do not plan to expose glib at the API level, if you mean that. So the
step will not introduce any g_xxx_yyy function in code that uses aRts. In
other words: I plan to maintain binary compatibility, which I have committed
myself to during the KDE3 development cycle.

However, a dependancy is a dependancy, and as such libmcop, libartsflow, ...
will gain an additional dependancy on glib-2.0.

   Cu... Stefan
  -* Stefan Westerfeld, stefan at (PGP!), Hamburg/Germany
     KDE Developer, project infos at *-         

More information about the kde-core-devel mailing list