Re: Parallel installs
- From: Owen Taylor <otaylor redhat com>
- To: gtk-devel-list redhat com
- Subject: Re: Parallel installs
- Date: 07 Jul 2000 16:09:45 -0400
I wrote:
> So, I propose the great move:
>
> /usr/include/glib.h => /usr/include/glib2/glib.h
> /usr/lib/glib/include => /usr/lib/glib2/include
> /usr/lib/glib/libglib.so => /usr/lib/glib/libglib-{1-3,2-0}.so
> glib-config => glib2-config
>
> /etc/gtk => /etc/gtk2
> /usr/share/local/*/*/gtk+.mo => /usr/share/local/*/*/gtk2.mo
> /usr/share/themes/*/gtk/ => /usr/share/themes/*/gtk2/
> /usr/include/gtk => /usr/include/gtk2/gtk
> /usr/include/gdk => /usr/include/gtk2/gdk
> gtk-config => gtk2-config
After going through and doing this, it occurs to me that
the API version for GTK+, as we do it currently, is the
major/minor pair, not just the major version number.
There are various approaches to dealing with this:
a) Ignore it, and worry about it when GTK+-2.2 comes along.
The worst that happens is that we have
/usr/lib/gtk
/usr/lib/gtk2
/usr/lib/gtk2.2
b) Substitute gtk20 for gtk2 above.
c) Go with a "version number in the path" approach for the
directories - /usr/include/gtk/2.0/. (But this doesn't
help for gtk-config.)
I'm sort of inclined to go with a), but that is probably
just laziness, on my part, since I have it done that way
already.
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]