Loïc Minier <[EMAIL PROTECTED]> writes:
> - separating with commas prevents passing options with commas; a sample
>use case which might be useful in the near future could be passing
>CFLAGS/LDFLAGS via DEB_BUILD_OPTIONS, and some of these flags require
>commas to reach the linker/asse
Hi,
On Wed, Jul 04, 2007, Russ Allbery wrote:
> At first glance, using a space-separated list of options would be a lot
> easier to parse since you could parse it entirely with internal make
> functions and not have to shell out to run sed.
A couple of updates:
- parsing a comma-separat
Loïc Minier <[EMAIL PROTECTED]> writes:
> My preferred policy change would be to state that DEB_BUILD_OPTIONS
> must be a space-separated list of keywords and parameters with
> parameters taking the form "name=value". The allowed chars for name
> and values would be limited to a-z, A-Z, 1-9,
On Tue, Jun 26, 2007, Bill Allombert wrote:
> I agree it is important that all debian/rules parse the options the same
> way. However "findstring" actually allow both spaces and commas as separator.
Sure, but $findstring(debug,nodebug) will match "debug" for example.
And it will also match build
On Tue, Jun 26, 2007 at 11:53:36AM +0200, Loïc Minier wrote:
> Package: debian-policy
> Version: 3.7.2.2
> Severity: normal
>
> Hi,
>
> In the discussions of bug #209008 (parallel building), Peter Samuelson
> explained he uses comma-separated keywords in DEB_BUILD_OPTIONS.
> Please doc
Package: debian-policy
Version: 3.7.2.2
Severity: normal
Hi,
In the discussions of bug #209008 (parallel building), Peter Samuelson
explained he uses comma-separated keywords in DEB_BUILD_OPTIONS.
Please document how keywords in DEB_BUILD_OPTIONS are allowed to be
separated.
I find
6 matches
Mail list logo
