From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter-devel@vger.kernel.org,
Giuseppe Longo <giuseppelng@gmail.com>,
Eric Leblond <eric@regit.org>
Subject: Re: [PATCH 1/2] iptables: utils: Add bash completion
Date: Wed, 2 Mar 2016 13:54:45 +0100 [thread overview]
Message-ID: <20160302125445.GA5129@salvia> (raw)
In-Reply-To: <56D6DB61.7070203@chello.at>
On Wed, Mar 02, 2016 at 01:24:01PM +0100, Mart Frauenlob wrote:
> On 02.03.2016 12:34, Pablo Neira Ayuso wrote:
> >On Thu, Feb 25, 2016 at 04:06:53PM +0100, Mart Frauenlob wrote:
> >> utils/iptables_bash_completion/README.md | 290 ++++
> >> utils/iptables_bash_completion/iptables | 2426 ++++++++++++++++++++++++++++++
> >
> >This is fair good amount of work, but this is also quite a bit of
> >new shell code to be maintained in our trees.
> >
> >Moreover, I was told that, in the specific case of debian, there is a
> >package (bash-completion) where you place this.
> >
> >So sorry, I'm not applying this.
>
> Hello Pablo,
>
> what a pitty! :-/
> Before writing this patch, I've asked the developers of bash completion for
> inclusion.
> For them it's fair to big and specific to maintain.
> They were worried about iptables becoming deprecated and them having dead
> code in their package.
> The only chance for inclusion, and that's not granted too, is to
> additionally write a test suite with tools I don't have any knowledge about
> yet - and to sign up as maintainer there.
> So they recommended me to request inclusion in iptables.
I see.
> I think this is a good piece of work, probably the best featured bash
> completion ever, and I'd wish to get it distributed.
> My abilities in that matter are limited.
>
> Of course I'd keep fixing bugs and add new iptables features (though I think
> there are not many to expect in the future, right?).
> If someone submits a bug report, I'll take care of it if anyhow possible.
> Just need to be notified by CC or so.
Then, my suggestion is to simplify this script in order to reduce the
maintainance burden.
One idea is to push into iptables some infrastructure so the script
can inquire iptables on available options. This would be simple C code
to be places on every extension to print the options. Then, add a tool
like iptables-completion that you can use to inquire what is possible
to get as options. Thus, we get a generic script that inquires
iptables, instead of having them all hardcoded into the script.
Would you explore this? I know Giuseppe Longo and Eric Leblond are
looking into this for nft following a similar approach.
next prev parent reply other threads:[~2016-03-02 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:06 [PATCH 0/2] iptables: utils: Add bash completion Mart Frauenlob
2016-02-25 15:06 ` [PATCH 1/2] " Mart Frauenlob
2016-03-02 11:34 ` Pablo Neira Ayuso
2016-03-02 11:57 ` Jan Engelhardt
2016-03-02 12:24 ` Mart Frauenlob
2016-03-02 12:54 ` Pablo Neira Ayuso [this message]
2016-03-02 19:26 ` Mart Frauenlob
2016-03-03 14:18 ` Mart Frauenlob
2016-02-25 15:06 ` [PATCH 2/2] iptables: Add bash completion to build routine Mart Frauenlob
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=20160302125445.GA5129@salvia \
--to=pablo@netfilter.org \
--cc=eric@regit.org \
--cc=giuseppelng@gmail.com \
--cc=mart.frauenlob@chello.at \
--cc=netfilter-devel@vger.kernel.org \
/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.
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 NNTP newsgroup(s).