On Thu, Jul 29, 2010 at 09:02:40AM +1000, Brian May wrote: > On 28 July 2010 22:06, James Vega <james...@debian.org> wrote: > > This happens because as soon as we see a non-debuild option, we break > > out of our option parsing and treat the rest as options for the other > > tools that get invoked. > > Errr... Not so fast at closing the bug - it isn't resolved yet...
It is from our end. It can be reopened and reassigned to
git-buildpackage if you like.
> The problem is that this command line is generated automatically by
> git-buildpackage, and git-buildpackage puts the "-i -I" options first,
> before any other options on given on the git-buildpackage command
> line.
>
> i.e.
>
> git-buildpackage --username value
>
> becomes
>
> debuild -i -I --username value
>
> Are you saying git-buildpackage needs to sort the options and put
> debuild options first?
Or it could rely on the user to specify all the args they want instead.
> That sounds like debuild needs to have a
^-- I assume you meant git-bp
> hardcoded list of what options debuild takes, which sounds very error
> prone and likely to break with new versions of debuild.
debuild isn't really a moving target, but if your suggested approach is
what git-buildpackage people decide to do, then yes they may need to do
that.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org>
signature.asc
Description: Digital signature
