Chris Carbaugh <[EMAIL PROTECTED]> writes:
> I have the source for both glib and gtk 1.2.6. I compiled and installed
> (./configure; make; make install) glib OK.
Just get the 1.2.6 RPMs and all your problems will be solved.
> Can I (via gnorpm) remove the 1.2.3 version of glib and gtk after the
> 1.2.6 versions are installed?
>
If you "upgrade" rather than "install" the RPMs then 1.2.6 will
automatically replace 1.2.3. via the command line, use "rpm -Uvh
<whatever>.rpm" to upgrade. I'm not sure about gnorpm.
> How do I tell existing programs to use the new 1.2.6 versions?
> Do I need to restart X (gnome/enlightenment)?
>
No, don't worry about it, it will just work fine.
> Should I just point the GLIB_CONFIG environment to the 1.2.6 version?
> If I do, where is the 1.2.6 lib?
> Do I just create/export the variable in my .bash_profile script?
>
No need, if you use the RPMs.
> This would create two versions of the same lib on my machine,won't that
> cause problems?
>
Yes, it can be problematic. You don't need 1.2.3 anymore though, so
that simplifies things.
> gnorpm seems like a great way to manage the software on my machine, but
> how long to I have to wait for newer versions of libraries to be
> available as RPM? It seems if glib/gtk 1.2.6 was available as an RPM,
> this process would be much easier.
>
They certainly are available, one simple way to get them is to upgrade
to Red Hat 6.2, but you can also just download the new GTK from 6.2
and install that. 6.2 has a program called up2date that can make this
a bit simpler. However since you have 6.0 you'll want to use the ftp
site:
ftp://ftp.redhat.com/pub/redhat/redhat-6.2/i386/RedHat/RPMS/
Havoc
--
To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null