bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug#400453: Makefile misses to clean .gmo-files in the clean target, so


From: Santiago Vila
Subject: Bug#400453: Makefile misses to clean .gmo-files in the clean target, so they get never be updated after updating an .po file (fwd)
Date: Sun, 26 Nov 2006 15:25:59 +0100 (CET)

Hello.

I received this from the debian bug system.

If this is not a bug, then it seems a documentation bug somewhere.

Thanks.

---------- Forwarded message ----------
From: Daniel Leidert <address@hidden>
To: Debian Bug Tracking System <address@hidden>
Date: Sun, 26 Nov 2006 12:45:14 +0100
Subject: Bug#400453: Makefile misses to clean .gmo-files in the clean target,
    so they get never be updated after updating an .po file

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-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]