From: Patrick McHardy <kaber@trash.net>
To: Kevin Fenzi <kevin@scrye.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables/libnftables packages for Fedora
Date: Mon, 13 Jan 2014 00:17:29 +0000 [thread overview]
Message-ID: <20140113001729.GB3251@macbook.localnet> (raw)
In-Reply-To: <20140112134024.2475a4f2@voldemort.scrye.com>
On Sun, Jan 12, 2014 at 01:40:24PM -0700, Kevin Fenzi wrote:
> 2. There is some question about the /etc/nftables/* scripts. In Fedora
> land, things in /etc/ should be config files, but these aren't really
> config files. They call nft without a full path (/usr/sbin/nft, etc).
> Should these really be in /usr/share ? or is it expected users will
> modify them? Could you clarify the use case there?
These files are to be included, they are mainly executable for easier
testing.
> 4. nftables sets make to '-s' (ie, silent) on subdirs. It's good for
> building packages to have verbose output in build logs. Would it be
> possible to remove that? If not I can patch it out here.
No problem adding an option to disable the silent output (I think
current autoconf supports this), but I'd like to keep it as default.
next prev parent reply other threads:[~2014-01-13 0:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 20:40 nftables/libnftables packages for Fedora Kevin Fenzi
2014-01-12 21:16 ` Arturo Borrero Gonzalez
2014-01-13 0:05 ` Kevin Fenzi
2014-01-13 0:18 ` Patrick McHardy
2014-01-13 0:11 ` Kevin Fenzi
2014-01-15 9:53 ` Pablo Neira Ayuso
2014-01-15 10:18 ` Arturo Borrero Gonzalez
2014-01-13 0:25 ` Patrick McHardy
2014-01-13 0:17 ` Patrick McHardy [this message]
2014-01-13 0:29 ` Patrick McHardy
2014-01-13 8:54 ` Jan Engelhardt
2014-01-13 9:09 ` Patrick McHardy
2014-01-13 19:18 ` Kevin Fenzi
2014-01-14 8:55 ` Patrick McHardy
2014-01-14 18:28 ` Kevin Fenzi
2014-01-14 18:34 ` Pablo Neira Ayuso
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=20140113001729.GB3251@macbook.localnet \
--to=kaber@trash.net \
--cc=kevin@scrye.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.