[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: pkg-config, glib2 etc.
From:       Mosfet <dan.duley () verizon ! net>
Date:       2003-03-16 21:04:21
[Download RAW message or body]

Opps, apparently I was wrong. When Havoc stated "There's nothing 
desktop-specific or desktop-related about pkg-config" on it's website I 
assumed it wasn't glib based. Turns out it is. This means using pkg-config 
also would require KDE to have glib, right? This is not desktop neutral 
software. 

On Sunday 16 March 2003 12:48 pm, Mosfet wrote:
> I don't really see any problem with requiring pkg-config. It's desktop
> independent software and wouldn't add additional dependencies or bloat to
> KDE itself. I'm not anti-anything-not-KDE ;-) Personally I think it's a
> good idea to look at how we can utilize the work done by other projects as
> long as the work is desktop independent software. I myself use the
> ImageMagick library in some of my apps. But just writing things in Glib and
> expecting KDE to require both toolkits is unreasonable, and as you said, an
> absurd thing to expect. This does not only apply to the soundserver,
> either.
>
> On Sunday 16 March 2003 11:54 am, George Staikos wrote:
> > Two more notes that I didn't notice in the responses to this thread:
> >
> >     Regarding pkg-config, I really don't think we have a choice for
> > 3.2.0. I think we should avoid it in 3.1.x for consistency, but too many
> > packages use it now.  We have to provide both pkg-config and
> > non-pkg-config checks in our configure until we have reason to require
> > that package at a version that certainly uses pkg-config.
> >
> >    Hopefully the glib dependency will disappear again.  I don't know if
> > it will though, and now arts is no longer a dependency for building
> > because of the move to use glib2.  I think the requirement of three
> > container sets (Qt, STL, and now glib) and two object models (Qt, glib)
> > is absurd.
> >
> > On Saturday 15 March 2003 23:12, Sean McGlynn wrote:
> > > Hello,
> > >
> > > I saw the discussions on core-devel recently about glib2 possibly being
> > > a requirement for aRts and, thus, KDE as a whole. I didn't actually see
> > > a final conclusive yes or no though. Now, I'm compiling CVS for the
> > > first time in many months. Arts wanted pkg-config as a requirement, so
> > > I downloaded and installed that. (I also noticed that pkg-config has
> > > its own copy of glib in the sources). Now Arts wants glib2 as well,
> > > which I don't have either yet. Before I proceed further, can I take it
> > > that glib2 *is* now a definite requirement for KDE3.2 and, also, can I
> > > expect Arts to come up with any more "you need this as well" messages.
> > >
> > > TIA
> > >
> > > Cheers,
> > > Sean
> >>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]