Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inetutils: new package
Date: Thu, 30 Oct 2014 14:58:01 +0200	[thread overview]
Message-ID: <20141030125801.GO1759@tarshish> (raw)
In-Reply-To: <CABbD_XDXmwU5QgT0i=g=zs_13fBWPdv2Bn+WfFZMDU_YX8er+Q@mail.gmail.com>

Hi K?roly,

On Thu, Oct 30, 2014 at 10:50:00AM +0100, K?roly Kasza wrote:
> Buildroot handles these "race conditions" with the <package>_DEPENDENCIES
> variables.
> I added Busybox as one (if selected), so Inetutils will always win over
> Busybox (that is probably
> unnecessary btw, Busybox should always be built before other packages - but
> I'm not sure in cases, where
> Busybox is built, but not the default init system nor shell).
> The other packages who provide anything related to inetutils are not yet
> added, but of course they can be added
> to act as dependencies.
> The question is, why do anybody want to compile and use different
> implementations of one program? I mean what
> could be the use case?

You assume that the user is doing a deliberate choice when enabling net-tools 
or inetutils. This is often not the case. A user bringing up a networking 
device is very likely to enable both packages. The version that eventually 
lands in the target will now be determined by the build order, and that may 
change from one build to another. We generally want make build results as 
consistent as possible. So, at the very least, we should warn the user in a 
comment that depends on BR2_PACKAGE_NET_TOOLS. I'm not sure this is enough, 
though.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-10-30 12:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 23:07 [Buildroot] [PATCH] inetutils: new package Karoly Kasza
2014-10-30  7:53 ` Jeremy Rosen
2014-10-30  9:37   ` Károly Kasza
2014-10-30  9:40     ` Baruch Siach
2014-10-30  9:50       ` Károly Kasza
2014-10-30 12:58         ` Baruch Siach [this message]
2014-10-31  9:29           ` Károly Kasza
2014-11-01 18:33             ` Károly Kasza
2014-11-01 19:01               ` Thomas Petazzoni
2014-11-01 19:07                 ` Károly Kasza
2014-11-01 20:31                   ` Thomas Petazzoni
2014-11-02 12:45                     ` Károly Kasza
2014-11-10 15:16                       ` Károly Kasza
2014-11-10 18:44                       ` Thomas Petazzoni
2014-11-10 21:46                         ` Károly Kasza

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=20141030125801.GO1759@tarshish \
    --to=baruch@tkos.co.il \
    --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