From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH v3] conf: Stop parsing options at first non-option argument
Date: Thu, 8 Aug 2024 14:44:41 +1000 [thread overview]
Message-ID: <ZrRNOU4ijXtzKJ7y@zatzit.fritz.box> (raw)
In-Reply-To: <20240808040251.2568850-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Thu, Aug 08, 2024 at 06:02:51AM +0200, Stefano Brivio wrote:
> Given that pasta supports specifying a command to be executed on the
> command line, even without the usual -- separator as long as there's
> no ambiguity, we shouldn't eat up options that are not meant for us.
>
> Paul reports, for instance, that with:
>
> pasta --config-net ip -6 route
>
> -6 is taken by pasta to mean --ipv6-only, and we execute 'ip route'.
> That's because getopt_long(), by default, shuffles the argument list
> to shift non-option arguments at the end.
>
> Avoid that by adding '+' at the beginning of 'optstring'.
>
> Reported-by: Paul Holzinger <pholzing@redhat.com>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-08 4:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 4:02 [PATCH v3] conf: Stop parsing options at first non-option argument Stefano Brivio
2024-08-08 4:44 ` David Gibson [this message]
2024-08-08 9:37 ` Paul Holzinger
2024-08-08 10:16 ` Stefano Brivio
[not found] ` <50d8ea4a-15ec-48a0-bc31-1e2a5139677b@redhat.com>
2024-08-08 12:30 ` Stefano Brivio
2024-08-08 18:33 ` Stefano Brivio
2024-08-09 0:47 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrRNOU4ijXtzKJ7y@zatzit.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
--cc=sbrivio@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).