Your message dated Mon, 27 Nov 2006 22:31:16 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400453: Makefile misses to clean .gmo-files in the clean
target, so they get never be updated after updating an .po file (fwd)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gettext
Version: 0.15-3
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It seems, the .gmo files are cleaned in the maintainer-clean target. But
they are created during make and so have to be cleaned in the
clean-target [1]. Otherwise they will never be updated except running
maintainer-clean, which will remove the whole build-environment in most
cases, because it's intended to remove the build environment.
Please fix this and foward this to upstream. Severity is set to
important according to the fact, that updates of .po files are not
merged into the .gmo files in the current situation.
Regards, Daniel
[1] See the autotools specs:
The GNU Makefile Standards specify a number of different clean rules.
Generally the files that can be cleaned are determined automatically by
Automake. Of course, Automake also recognizes some variables that can be
defined to specify additional files to clean. These variables are
MOSTLYCLEANFILES, CLEANFILES, DISTCLEANFILES, and MAINTAINERCLEANFILES.
As the GNU Standards aren't always explicit as to which files should be
removed by which target, we've adopted a heuristic which we believe was
first formulated by Franccedil;ois Pinard:
* If make built it, and it is commonly something that one would
want to rebuild (for instance, a .o file), then mostlyclean
should delete it.
* Otherwise, if make built it, then clean should delete it.
* If configure built it, then distclean should delete it
* If the maintainer built it, then maintainer-clean should delete
it.
We recommend that you follow this same set of heuristics in your
Makefile.am.
- -- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.09060920
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages gettext depends on:
ii gettext-base 0.15-3 GNU Internationalization utilities
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
Versions of packages gettext recommends:
ii curl 7.15.5-1 Get a file from an HTTP, HTTPS, FT
ii lynx 2.8.5-2sarge2.1 Text-mode WWW Browser
ii wget 1.10.2-2 retrieves files from the web
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFaX5Km0bx+wiPa4wRAsf6AKDI1O0rDedOtWt64Mu4/WjVzlHxdwCdFo32
yFQxrAtXFregOgMbe9hfWAQ=
=xmrF
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Mon, 27 Nov 2006, Bruno Haible wrote:
> Daniel Leidert <[EMAIL PROTECTED]> wrote:
> > It seems, the .gmo files are cleaned in the maintainer-clean target. But
> > they are created during make and so have to be cleaned in the
> > clean-target [1].
>
> The text you cite is a heuristic list of rules of thumb. A more important
> text are the GNU Coding Standards, which say:
>
> `clean'
> Delete all files in the current directory that are normally
> created by building the program. Also delete files in other
> directories if they are created by this makefile. However, don't
> delete the files that record the configuration. Also preserve
> files that could be made by building, but normally aren't because
> the distribution comes with them. ...
>
> The *.gmo files are part of the distribution, hence must not be removed by
> "make clean". (If they did, then a user who does not have the GNU gettext
> tools installed could not do
> "./configure; make; make clean; make; make install".)
>
> > Otherwise they will never be updated
>
> The *.gmo files don't need to be updated often. Earlier the Makefile rules
> updated the *.gmo files each time the *.po files changed, and the *.po files
> each time the .pot file changed, and the .pot file each time the sources
> changed. The maintainers were annoyed by this - in their eyes - useless
> waste of CPU cycles.
>
> Santiago Vila writes:
> > If this is not a bug, then it seems a documentation bug somewhere.
>
> The *.gmo files are required when a maintainer does a distribution.
> Therefore see documentation section "Release Management". It documents
> a Makefile target 'update-po'. If you look into the Makefile, you will
> also see a Makefile target 'update-gmo'.
Thanks a lot for the explanations. Closing then.
--- End Message ---
