From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7556] New: make interactive CLI optional for nftables
Date: Sun, 26 Oct 2014 17:58:00 +0000 (UTC) [thread overview]
Message-ID: <bug-7556-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7556
Summary: make interactive CLI optional for nftables
Product: buildroot
Version: 2014.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: alex at digriz.org.uk
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5744
--> https://bugs.busybox.net/attachment.cgi?id=5744
patch to make nftables cli optional
nftables requires readline (and thus in turn ncurses) which adds considerably
to the size of the root filesystem (~500kB for MIPS).
Did a bit of work and we can now make it optional (by default it is not
enabled).
Is this patch reasonable, need me to do anything else to it for it to be
considered for buildroot. I am also reaching out to the nftables team to see
about upstreaming this.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-10-26 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 17:58 bugzilla at busybox.net [this message]
2014-10-26 18:06 ` [Buildroot] [Bug 7556] make interactive CLI optional for nftables bugzilla at busybox.net
2014-12-06 19:28 ` bugzilla at busybox.net
2014-12-06 20:23 ` bugzilla at busybox.net
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=bug-7556-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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