From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] iputils: resolve musl compatibility
Date: Thu, 21 Jan 2016 09:17:40 +0100 [thread overview]
Message-ID: <20160121091740.795734ad@free-electrons.com> (raw)
In-Reply-To: <CAFt09wOgaktzEG+GVhf=fEfC=bnQdqAYLF3kn8fj7A10emMEBQ@mail.gmail.com>
Matt,
On Wed, 20 Jan 2016 18:27:17 -0600, Matthew Weber wrote:
> > You don't explain here why you are adding libcap as a mandatory
> > dependency. USE_CAP=no still exists, and it stills works, so there is
> > no reason to make libcap a mandatory dependency.
>
> That's fair, I was attempting to cleanup assumptions in the build to
> build the standard config without and disables (except deprecated
> items). I will update per the below suggestion to enable that option
> with libcap is selected.
Our policy in general is to try to build things with minimal
dependencies by default. So if it can build with libcap, then it should
be built without libcap by default, unless libcap is explicitly
selected, of course.
Like any rule, there are some exceptions, like if a package can build
without a dependency, but becomes really useless. I don't think it's
the case of iputils.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-21 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 12:20 [Buildroot] [PATCH v3 1/1] iputils: resolve musl compatibility Matt Weber
2016-01-20 20:45 ` Thomas Petazzoni
2016-01-21 0:27 ` Matthew Weber
2016-01-21 8:17 ` Thomas Petazzoni [this message]
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=20160121091740.795734ad@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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