Hi! On Fri, 2010-01-22 at 11:21:13 +0100, Raphael Hertzog wrote: > > Please add --single-debian-patch to the list of options to be passed to > > dpkg-source only. > > No, I'm not going to add all the dpkg-source options to dpkg-buildpackage. > And that option in particular is meant to be stored in > debian/source/options and not to be given at build time.
I agree with that. > I would like however to enhance dpkg-buildpackage to support passing > arbitrary options to each sub-command but I'm not sure what would > be the proper syntax. Maybe something like this: > > dpkg-buildpackage --to-dpkg-source <opt1> [<opt2> ...] -- -us -uc > (it would also have --to-dpkg-genchanges) > > OR > > dpkg-buildpackage --to-dpkg-source <opt1> --to-dpkg-source <opt2> -us -uc > > OR > > dpkg-buildpackage --dpkg-source-opt="<opt>" -us -uc > Guillem (or anyone reading this), do you have any preference/suggestion on > the syntax for such a feature ? What about “-Obackend,option1,option2” (and --bakend-options or similar, or -o instead of -O) in a similar way as how gcc is doing it? Other variants where the backend is part of the argument could be possible too, in case we would need to pass commas to the backends. This way we don't pollute the option space, and even if we start using another backend it does not increase them either. regards, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
