Bug#430649: New proposed wording for DEB_BUILD_OPTIONS

[Guillem Jover <guillem@debian.org>]

Hi,

On Sun, 2007-12-30 at 19:23:58 -0800, Russ Allbery wrote:
> Okay, here's a revised proposal to address both Bug#209008 (parallel) and
> Bug#430649 (DEB_BUILD_OPTIONS parsing).  This proposal does the following:

> --- orig/policy.sgml
> +++ mod/policy.sgml

> +	<sect id="debianrules-options">
> +	  <heading><file>debian/rules</file> and
> +	    <tt>DEB_BUILD_OPTIONS</tt></heading>
> +
> +	  <p>
> +	    Supporting the standardized environment variable
> +	    <tt>DEB_BUILD_OPTIONS</tt> is recommended.	This variable can
> +	    contain several flags to change how a package is compiled and
> +	    built.  Each flag must be in the form <var>flag</var> or
> +	    <var>flag</var>=<var>options</var>.	 If multiple flags are
> +	    given, they must be separated by whitespace.<footnote>
> +	      Some packages support any delimiter, but whitespace is the
> +	      easiest to parse inside a makefile and avoids ambiguity with
> +	      flag values that contain commas.
> +	    </footnote>
> +	    <var>flag</var> must consist only of lowercase letters
> +	    (<tt>a-z</tt>), numbers (<tt>0-9</tt>), and the characters
> +	    <tt>-</tt> and <tt>_</tt> (hyphen and underscore).
> +	    <var>options</var> must not contain whitespace.  The same
> +	    tag should not be given multiple times with conflicting
> +	    values.  Package maintainers may assume that
> +	    <tt>DEB_BUILD_OPTIONS</tt> will not contain conflicting tags.
> +	  </p>

Could this be changed to say that flags start with «[a-z]» optionally
followed by 0 or more «[a-z][0-9]-_»?

regards,
guillem