[debhelper-devel] [PATCH] Put extra options after dh-generated ones

Dmitry Bogatov KAction at gnu.org
Sun Aug 30 19:47:23 UTC 2015


> Thanks for your interest.

Thanks for your maintenance.

> I have two concerns about this patch.  Please consider the following
> example:
> 
>   dh $@ --with foo,bar,baz
> 
> If the "foo" module passes "--" to dh_shlibdeps, then "bar" nor "baz"
> can pass a debhelper option dh_shlibdeps.  If "bar" also want to pass a
> "--" to dh_shlibdeps, then the modules cannot be used together.
> 
> Accordingly, I do not think your patch solves your use-case sufficiently
> to the extend where we can recommend people to use it in general.

I understand your concerns.

> Separately, applying this patch would also mean that options passed by
> the user is now overruled by the sequencer.  I am not entirely sure if
> this make sense
> 
> As for moving forward.  Maybe we need a different method for passing
> "non-options" that are passed after an "--"?  It seems like it would
> solve your use-case and interact better with other sequence extensions.

Clearly, we can't just drop '--', but maybe we should deprecate it.

What about tweak to init() function to automatically handle
two options -- `--raw-pre` and `--raw-post`?

Will this solution be generic enough, or we should support
`--raw-mangle` option, that can be given arbitrary perl code or smth like
this?

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debhelper-devel/attachments/20150830/ce2c6068/attachment.sig>


More information about the debhelper-devel mailing list