Re: is GNU gettext now a required prerequisite for GNOME?

["Brandon S. Allbery" <allbery ece cmu edu>]

| > I've been relying on --with-included-gettext because the choice is upgrading
| > gettext to a new version that breaks everything else in ECE vs. saving some 
| > space in GNOME.  Do I now have to go ahead and break everything non-GNOME to
| > continue?
| 
| Why not install gnu-gettext in a non-standard location for use
| with GNOME hacking?  I have to futz around with two versions
| of gtk, why is gettext any different?
+--->8

Because undergrads pop onto hilfy and do ECE builds on it; they'll get the
wrong libintl, same as they get the wrong Gtk+, libz, libpng, etc. now.
(Which hasn't been too much of a problem because we don't use that many
graphical programs, but ddd was seriously messed up by finding Xaw3d on
my system at one point....)

I'm currently working on upgrading our released gettext package in order to
test it on various systems (thanks to AFS readonly volumes, so only the
systems I explicitly sync it onto will see the new version).  I'm *not*
happy about a global upgrade to a package version that has a nasty-sounding
README-alpha in it.

BTW, a warning to anyone building the new gettext (I'll be sending this on
to the proper people as soon as I look them up):  unless you already have
a share/gettext/{intl,po} directory tree built, gettext will install wrong.
The install will succeed, but gettextize will screw things up mightily....
Simply precreate the target directories and it will work properly.

(Which doesn't help my confidence about requiring it when we're supposedly
winding toward GNOME 1.0....)

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
electrical and computer engineering					 KF8NH
carnegie mellon university	      ["God, root, what is difference?" -Pitr]