Nope, it was pkgconfig.  I didn't notice that you could use the built-in
one :-P

On Sun, Mar 16, 2003 at 09:19:18PM -0700, tech@bishop.dhs.org wrote:
> 
> To insert my 'real life' experience, here, I just got done installing
> kde 3.1 on solaris, and had to explicitely install glib for one of the
> libraries that kde depends on (sorry, don't have my notes in front of
> me, I seem to remember it being an audio lib) , as we don't (nor will 
> we ever) use pam :-)
> 
> Basically, 1) distinctly *not* everybody has glib and 2) we seem to be
> getting it anyways...
> 
> On Sun, Mar 16, 2003 at 10:01:24PM -0600, Mosfet wrote:
> > BTW, I apologize for the "what are you smoking?" comment ;-)
> > 
> > Just because it's in PAM, tho, does not mean we should require KDE developers 
> > to know it if they want to work on parts of the KDE core API. It is not known 
> > by many developers.
> >  
> > On Sunday 16 March 2003 9:25 pm, Mosfet wrote:
> > > LOL. Just checked the RedHat packages and, yep - PAM requires glib. *sigh*
> > >
> > > ...snip...
> > 
> >  
> > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>  
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<