#708163 schroot should treat options after non-option as non-option

Package:
schroot
Source:
schroot
Description:
Execute commands in a chroot environment
Submitter:
Ian Jackson
Date:
2021-03-23 17:57:05 UTC
Severity:
normal
#708163#5
Date:
2013-05-13 16:43:40 UTC
From:
To:
$ schroot -c unstable-i386 id -u
E: required parameter is missing in 'user'

This is a bit silly.  It would be better if schroot stopped processing
schroot options as soon as it saw the command (ie, the first
non-option).

Thanks,
Ian.
#708163#10
Date:
2013-05-13 22:25:47 UTC
From:
To:
You can use -- to separate options from non-options explicitly.  We are
using libboost-program-options for the options parsing; it does provide
for customising the parsing process somewhat, but I'm not certain how
difficult (or possible) such a change will be.  I'll certainly look
into it.


Regards,
Roger
#708163#15
Date:
2013-05-14 22:40:54 UTC
From:
To:
Roger Leigh writes ("Re: [buildd-tools-devel] Bug#708163: schroot should treat options after non-option as non-option"):

Sorry, yes, I should have said I knew that.

Hmm.  I had a look at the online docs for Boost 1.53.0 and it doesn't
seem to be able to do it.  The obvious place for it would be one of
the flags in boost::program_options::command_line_style::style_t.  I
also looked for a way to use a positional parameter callback to abort
the command line processing loop, but didn't find out.

Should I file a wishlist bug against the boost library and set this
one to block it ?

Thanks,
Ian.
#708163#20
Date:
2014-01-02 17:44:17 UTC
From:
To:
That would be appreciated, thanks.  Sorry for the delay on my part.


Regards,
Roger