mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] Install tar from CONFIG_TAR to /bin/ instead /usr/bin/
Date: Wed, 12 Apr 2017 18:00:51 +0200	[thread overview]
Message-ID: <20170412160051.2kjghmmzfwdwpya7@pengutronix.de> (raw)
In-Reply-To: <77e60ebc-7d09-a74a-2682-e1449117abb0@gr13.net>

On Wed, Apr 12, 2017 at 10:36:46AM +0200, Enrico Weigelt, metux IT consult wrote:
> On 05.04.2017 10:04, Gavin Schenk wrote:
> > Debian and Ubuntu install tar in /bin. This is the same in ptxdist when
> > BUSYBOX_TAR is selected. If CONFIG_TAR is selected ptxdist installs tar
> > to /usr/bin.
> 
> All the different unices I remember from the last two decades had tar
> in /bin (as it's considered system util), so I'm in favour of that.
> 
> OTOH, some folks in ptxdist world might be expecting the standalone tar
> in /usr/bin - so, perhaps make it configurable.
> 
> An interesting question is whether there could be any reason for having
> both of them on one system. Maybe systems w/ optional packages, where
> only some users in the field might install the full tar, if bb'es
> trimmed-down one isn't sufficient.

Since the /usr merge, this discussion is obsolete.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-04-12 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  8:04 Gavin Schenk
2017-04-12  8:36 ` Enrico Weigelt, metux IT consult
2017-04-12 16:00   ` Robert Schwebel [this message]
2017-04-18  5:45     ` Schenk, Gavin

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=20170412160051.2kjghmmzfwdwpya7@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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