Date: 10 Aug 1998 12:06:38 +0200 From: Thomas Gellekum <tg@ihf.rwth-aachen.de> To: asami@FreeBSD.ORG (Satoshi Asami) Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/x11/pygtk Makefile Message-ID: <87ogttb175.fsf@ghpc6.ihf.rwth-aachen.de> In-Reply-To: asami@FreeBSD.ORG's message of "Mon, 10 Aug 1998 02:49:16 -0700 (PDT)" References: <199808100949.CAA01115@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
asami@FreeBSD.ORG (Satoshi Asami) writes: > * > glib.h is in /usr/local/include/glib. Perhaps it needs to be changed after > * > glib was updated. > * > * SEP, I think. > > SEP? ;) Granted, part 3 of THGTTG was not the best, but important concepts like ``Someone Else's Problem'' should definitely stay in the collective subconscious. ;-) > * Works fine with the `old' gtk port. Judging from the > * PLISTs, gtk11 installs its own glib.h into /usr/local/include, whereas > * /usr/local/include/glib/glib.h comes from the glib port. Vanilla? > > Oops. I saw "glib.h" so I just assumed it comes from the glib port. > > So you're saying it should work if I reinstall gtk? Depends on whether configure finds /usr/local/bin/gtk-config first or /usr/X11R6/bin/gtk-config. I hate it. > * That's a gtk vs. gtk11/glib issue. py-gtk uses gtk (1.0.[2-5]) for > * now; the next version will have support for gtk11. I don't know if > * there are major differences. I'll look after it when the upgrade to > * gtk-1.1 has been committed. > > Well if something needs "support" for gtk11, they should be > incompatible. Well, the author of py-gtk just wrote he'd be moving on to gtk-1.1. This may or may not mean that gtk-1.1 is incompatible to gtk-1.0, I can't tell. Why would we need different ports for the two versions if they were compatible? tg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ogttb175.fsf>