Re: glib install problems


Anthony DiSante <orders nodivisions com> writes:

> Well, I'm not clueless, but that doesn't mean I know everything,
> either. Why don't you recommend fiddling with the stuff in /usr?

Most binary packages install themselves to the /usr prefix, while
source packages go to /usr/local. By not touching any files in the
/usr prefix you can be sure that all files there are handled by the
package manager. It's a simple rule that can be quite helpful.

> I would rather have just one version installed, but I gather that
> removing the old version is going to break some of my currently
> installed apps.  (As I said, I temporarily removed just a few files
> from /usr/lib/ and already lots of apps won't run.)

If you provided the new versions in /usr/local/lib and configured the
linker correctly, your apps should have used the gtk+-2.4. Since this
library is backward-compatible, this should just work.

> What is the long-term solution?  Is it possible to remove the old
> version completely, and somehow tell my already-installed apps to use
> the new version from now on?

Sure, 'make uninstall' the old versions or remove them by other means
and then, either install the new ones into the /usr prefix or tell the
compiler and linker to look into /usr/local.

> from source, and glib/gtk is the only thing that consistently gives
> me problems. I should be able to just have them installed in one
> place, and upgrade them when they need it, without having to worry
> about breaking all my apps or having to manage two separate
> installations in two places.

Why don't you just do that then? If you have the old versions
installed from source in /usr, why do you put the new ones to
/usr/local ?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]