From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inetutils: new package
Date: Mon, 10 Nov 2014 19:44:04 +0100 [thread overview]
Message-ID: <20141110194404.15efb715@free-electrons.com> (raw)
In-Reply-To: <CABbD_XBJzp-ibX5bMB_SfxndbPQs_R5+gqTaPrwAWJFmz5Nj5A@mail.gmail.com>
Dear K?roly Kasza,
On Sun, 2 Nov 2014 13:45:19 +0100, K?roly Kasza wrote:
> I wrote a small script to analyse which files are redundant, and if they
> will be overwritten or not.
> I ran it against busybox, net-tools, iputils, rsh-redone, sysklogd and
> whois because I found that these
> packages may overlap with inetutils' tools.
>
> The same filename lines mean that an other file with the same name, but
> with a different path exists
> (the compared package's path is in the brackets).
> The same path lines mean that it would be overwritten at install.
>
> busybox:
> Found same filename /usr/bin/dnsdomainname (/bin/dnsdomainname)
> Found same filename /usr/bin/ping (/bin/ping)
> Found same filename /usr/bin/hostname (/bin/hostname)
> Found same filename /usr/bin/ifconfig (/sbin/ifconfig)
> Found same filename /usr/libexec/syslogd (/sbin/syslogd)
> Found same path /usr/bin/traceroute
> Found same path /usr/bin/tftp
> Found same path /usr/bin/logger
> Found same path /usr/bin/telnet
> Found same filename /usr/libexec/inetd (/usr/sbin/inetd)
>
> net-tools:
> Found same filename /usr/bin/dnsdomainname (/bin/dnsdomainname)
> Found same filename /usr/bin/hostname (/bin/hostname)
> Found same filename /usr/bin/ifconfig (/sbin/ifconfig)
> Found same path /usr/share/man/man1/dnsdomainname.1
> Found same path /usr/share/man/man1/hostname.1
>
> iputils:
> Found same filename /usr/bin/ping6 (/bin/ping6)
> Found same filename /usr/bin/ping (/bin/ping)
>
> rsh-redone:
> Found same path /usr/bin/rlogin
> Found same path /usr/bin/rsh
>
> sysklogd:
> Found same filename /usr/libexec/syslogd (/sbin/syslogd)
>
> whois:
> Found same path /usr/share/man/man1/whois.1
> Found same path /usr/bin/whois
>
> I think a solution would be to disable inetutils' redundant tools:
> whois, sysklogd, rlogin(d), rsh(d), ping, ping6, hostname, dnsdomainname,
> ifconfig, hostname.
>
> After that, the only utility, that's not overwritten would be inetd from
> busybox, where a post-install hook
> could simply alter the busybox symlink to point to inetutils' version
> instead.
>
> I'm waiting for your opinions!
Personally, I think we should keep all of those tools enabled, and
simply fix the installation path, especially since inetutils is often
the only one doing "weird" things, and all of the other packages agree
on the location for all tools
First, for the "Found same path" cases above, I believe the solution is
fairly easy: just make sure inetutils depends on the relevant packages
so that they get overriden. For busybox it's easy, we always want the
inetutils tools to override the busybox one. For the other packages, it
might need a little bit more discussion as it's not immediately clear
which package has the "best" implementation for each of the tools.
Now, for the "Found same filename" cases, the situation is quite clear:
* dnsdomainname: both busybox and net-tools install it to /bin,
inetutils is the only one to choose /usr/bin. So the solution is to
move it to /bin in inetutils.
* ping: both busybox and iputils install it to /bin, so same solution
as above.
* hostname: both busybox and net-tools install it to /bin, so same
solution.
* ifconfig: both busybox, and net-tools install it to /sbin, so same
solution.
* syslogd: both busybox and sysklogd install it to /sbin, so same
solution.
You can also try to pass --exec-prefix=/ in INETUTILS_CONF_OPTS and see
if it improves the situation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-10 18:44 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
2014-11-02 12:45 ` Károly Kasza
2014-11-10 15:16 ` Károly Kasza
2014-11-10 18:44 ` Thomas Petazzoni [this message]
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=20141110194404.15efb715@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