Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] iptables: enable basic kernel options
Date: Tue, 28 Oct 2014 23:11:27 +0100	[thread overview]
Message-ID: <5450148F.5000906@mind.be> (raw)
In-Reply-To: <20141028191014.64709e21@free-electrons.com>

On 28/10/14 19:10, Thomas Petazzoni wrote:
> Dear Gustavo Zacarias,
> 
> On Tue, 28 Oct 2014 15:04:59 -0300, Gustavo Zacarias wrote:
>> On 10/28/2014 03:02 PM, Thomas Petazzoni wrote:
>>
>>> For this one, I don't know. Back some time ago, Peter said that his
>>> preference was to not enforce too much stuff in terms of kernel
>>> configuration options in linux/linux.mk. I think the idea is that it's
>>> something that can quickly become very complicated if you want to
>>> handle all the kernel config options that all packages might need. It's
>>> also being forced without the user being capable of doing anything
>>> against that: those KCONFIG_ENABLE_OPT calls are done even if the user
>>> passes a custom configuration file.
>>>
>>> But back at the time, we only had the CONFIG_AEABI option being
>>> handled. Now it's true we already have ktap, systemd, smack being
>>> handled, and many other things related to appended DTB, initramfs, and
>>> more. So it seems like the iptables/xtables-addons proposal from
>>> Gustavo are not really creating a precedent.
>>>
>>> Peter, what is your position on this?
>>
>> Unfortunately it's not optional for xtables-addons, it needs the
>> iptables bits for the xtables bits in the other patch.
>> We could just get them together or ditch the package since it will
>> result in a build failure.
> 
> As said on IRC, if those options are needed at build time for
> xtables-addons, it makes a very good case for having them.

 I completely agree with that reasoning.

 Actually, I think it's just the ktap and smack modifications that are really
controversial. The others are either required for building, or they are system
configuration options and for those it's logical to propagate to the kernel config.


 Regards,
 Arnout

> 
> Peter, OK ?
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-10-28 22:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 21:10 [Buildroot] [PATCH 1/3] xtables-addons: new package Gustavo Zacarias
2014-10-21 21:10 ` [Buildroot] [PATCH 2/3] iptables: enable basic kernel options Gustavo Zacarias
2014-10-28 18:02   ` Thomas Petazzoni
2014-10-28 18:04     ` Gustavo Zacarias
2014-10-28 18:10       ` Thomas Petazzoni
2014-10-28 22:11         ` Arnout Vandecappelle [this message]
2014-10-21 21:10 ` [Buildroot] [PATCH 3/3] xtables-addons: enable necessary " Gustavo Zacarias
2014-10-22 17:18 ` [Buildroot] [PATCH 1/3] xtables-addons: new package Arnout Vandecappelle
2014-10-22 22:38   ` Gustavo Zacarias
2014-10-28 22:18     ` Arnout Vandecappelle
2014-10-23 11:07   ` Gustavo Zacarias
2015-01-10 17:55 ` Thomas Petazzoni

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=5450148F.5000906@mind.be \
    --to=arnout@mind.be \
    --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