From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inetutils: new package
Date: Sat, 1 Nov 2014 21:31:17 +0100 [thread overview]
Message-ID: <20141101213117.6673aa69@free-electrons.com> (raw)
In-Reply-To: <CABbD_XA35CzC9nWkUnXnidJFEnZ0=yV1wd1f8FytjPKunw=uQg@mail.gmail.com>
Dear K?roly Kasza,
On Sat, 1 Nov 2014 20:07:25 +0100, K?roly Kasza wrote:
> it is unpleasant indeed.
> What is the Buildroot recommended method for these issues?
> Should I modify the install target to overwrite the existing tools?
I'd say it depends on the cases. Can you do a summary of the situation,
i.e what tools inetutils installs and where, and how it compares with
the installation location of the same tools by Busybox? That might help
see how far we are, and what is the appropriate course of action.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-01 20:31 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
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 [this message]
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=20141101213117.6673aa69@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