> That's not completly true. Some files are installed by both, like
> glib-config, etc..
No, glib 2.0 uses pkgconfig.
If there are any files that both try to install, it's a bug and should
be reported to bugzilla.gnome.org. You're supposed to be able to have
both glib 1.2.10 and glib 2.0 installed into the same prefix without any
problems (and ditto for gtk and the upcoming gnome2 stuff).
> If you are talking about the symlink from /sw/include/gtk to
> /sw/include/gtk-1.2 - yeah, that may have to go, but that's not
> affecting glib. In fact I am running with glib-1.2 and glib-2.0 next to
> each other in /sw for quite some time now, I just never packaged it up.
The problem comes when you try to build something that uses glib-2.0 (or
gtk-2.0 or whatever). glib-1.2.10-3.info does:
(cd %i/include && ln -s glib-1.2/* .)
so something that wants to be including glib 2.0's glib.h could end up
with glib-1.2's instead if /sw/include is in the CPPFLAGS (which it
always is, right?)
-- Dan
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
