GNU bug report logs - #7656
MANS primary accepts too many prefixes

Previous Next

To reply to this bug, email your comments to 7656 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: bug-automake <at> gnu.org
Subject: MANS primary accepts too many prefixes.
Date: Thu, 16 Dec 2010 22:51:15 +0100

Currently, the MANS primary accept *all* the standard automake
builtin prefix dirs (from lib and bin to pkglibexec and sysconf).

IMHO it should accept only man and man{1..9} (maybe doc? but I'd
rather say no).

Thanks,
   Stefano

Message #8 received at 7656 <at> debbugs.gnu.org (full text, mbox):

From: Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 7656 <at> debbugs.gnu.org
Subject: Re: bug#7656: MANS primary accepts too many prefixes.
Date: Fri, 17 Dec 2010 07:00:03 +0100

* Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:51:15PM CET:
> Currently, the MANS primary accept *all* the standard automake
> builtin prefix dirs (from lib and bin to pkglibexec and sysconf).
> 
> IMHO it should accept only man and man{1..9} (maybe doc? but I'd
> rather say no).

This one is less easy than the other one, but again the question to
be answered is: is it completely and totally impossible that a developer
has a decent use case for something you would like to forbid?  If no,
then why forbid it?

Thanks,
Ralf

Message #11 received at 7656 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
Cc: 7656 <at> debbugs.gnu.org
Subject: Re: bug#7656: MANS primary accepts too many prefixes.
Date: Fri, 17 Dec 2010 12:19:03 +0100

On Friday 17 December 2010, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:51:15PM CET:
> > Currently, the MANS primary accept *all* the standard automake
> > builtin prefix dirs (from lib and bin to pkglibexec and sysconf).
> > 
> > IMHO it should accept only man and man{1..9} (maybe doc? but I'd
> > rather say no).
> 
> This one is less easy than the other one, but again the question to
> be answered is: is it completely and totally impossible that a developer
> has a decent use case for something you would like to forbid?  If no,
> then why forbid it?
>
Note that we won't really forbid it, we'll just require the developer
to be more explicit/verbose about what he's doing if that's a thing
that "smells fishy" to automake; for example, automake will be required
to error out on this:
  doc_MANS = foo.1
but not on this:
  my_mandir = $(docdir) # we want manpages installed in $(docdir) because ...
  my_man_MANS = foo.1

And note that the current automake already behaves this way with other
primaries such as `PROGRAMS', so that:
  lib_PROGRAMS = foo
gives an error, but:
  foodir = $(libdir)
  foo_PROGRAMS = foo
does not.  This is by design, and it's a good design IMHO.

Regards,
   Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.