5 Feb 06:38
Re: gcm 2.0.4 has very buggy build scripts
Andrew Lau <netsnipe <at> debianplanet.org>
2003-02-05 05:38:49 GMT
2003-02-05 05:38:49 GMT
On Tue, Feb 04, 2003 at 07:07:18PM +0100, Philip Van Hoof wrote: > > 1. i18n support is severely broken, as each locale is incorrectly > > being installed as: > > "/usr/share/locale/$LANG/LC_MESSAGES/@GETTEXT_PACKAGE@.mo". > > @GETTEXT_PACKAGE@ is not being substituted with "gcm". I've had to > > disable i18n in my packages altogether due to this. > > i18n seems to work here. It is also very wierd that anything would > go wrong because there is almost NO configuration that has to be > done when you use the automake-tools. The people of gnome-i18n also > maintain changes about the i18n support. So if something as huge as > that would be wrong, then they would have told me a long time ago .. Dear Philip, So i18n in gcm can find the appropriate i18n locales even though you have files such as /usr/share/locale/de/LC_MESSAGES/@GETTEXT_PACKAGE@.mo instead of gcm.mo? Yours sincerely, Andrew "Netsnipe" Lau PS: Have you corrected the clear clipboard bug yet? Do you have a patch I can apply on 2.0.4 to fix it? Thanks. -- -- --------------------------------------------------------------------------- * Andrew "Netsnipe" Lau Computer Science & Student Rep, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * <netsnipe(+)debianplanet.org\0> <alau(+)cse.unsw.edu.au\0> *(Continue reading)
> There are a couple of problems I'm seeing though. First when I opened
> the tarball, the configure script didn't work. The symlinked libtool and
> automake scripts will not work. End users and package compilers will
> need local copies of those tools in the release.
I would be more than happy if somebody with the proper knowledge of
buildscripts could help me. If you see fixes that you can do then do not
hesitate to contact me and provide patches.
> Do you think you can fix this up and make a new release?
The next release that I will be responsible for will be the 2.1.0 or
unstable release. I don't know if this release will get packages by the
packagers (debian and redhat). I will also maintain the next stable
branche called 2.2.0. This branche will be developed in parallel with
2.1.0 of course. When a first release of 2.2.0 will be finished: I don't
know
RSS Feed