bug-standards
[Top][All Lists]
Advanced

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

Re: Behaviour of Build / Configure in GNU programs


From: John Darrington
Subject: Re: Behaviour of Build / Configure in GNU programs
Date: Wed, 8 Jul 2015 15:22:44 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Jul 08, 2015 at 02:53:03PM +0200, Mathieu Lirzin wrote:
     John Darrington <address@hidden> writes:
     
     > Lot's of things are acceptable, but only a few are unacceptable.
     > How could we possibly list all the acceptable ones?
     >
     > As I see it, the GCS is not supposed to be a tutorial document.
     > Gnulib is a rather special case of a project, so I don't think
     > it is a good example to use anyway.
     
     Sorry if my words were poorly chosen, but my point was not about listing
     what is acceptable or transforming the GCS in a tutorial.  What I mean
     is that when I read:
     
     "Don't allow any part of the build or configure process to open a
     network connection in order to download files remotely"
     
     I am confused about knowing if this extends implicitly to the
     "pre-configure" process.  In that regard, it can let readers think that
     the usage of Gnulib 'bootstrap' script is not compliant with the GCS.
     
Ok.  How about appending this clarification:

"This restriction does not apply to pre-configuration scripts or programs 
intended for use only by developers of the package."



-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

Attachment: signature.asc
Description: Digital signature


reply via email to

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