From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] executables in /usr/bin vs /bin
Date: Thu, 11 Feb 2016 09:30:30 +0100 [thread overview]
Message-ID: <20160211083030.GA6633@pengutronix.de> (raw)
In-Reply-To: <20160210174804.GA9521@archie.tuxnet.lan>
On Wed, Feb 10, 2016 at 06:48:04PM +0100, Clemens Gruber wrote:
> Hi,
>
> in the proposed version bump for procps, the default path changed to
> /bin instead of /usr/bin. In my patch I just renamed the paths. But
> maybe that's the wrong approach and we should keep all binaries in
> /usr/bin ?
>
> Debian on the other hand puts most of them in /usr/bin and a few into
> /bin.
>
> Should I send a v2 with all rules changed like this?
> @$(call install_copy, procps, 0, 0, 0755, /bin/free, /usr/bin/free)
That would be ... $(PROCPS_PKGDIR)/bin/free, /usr/bin/free)
And yes, I'd like a v2 like this. I'm not sure if any of these paths are
hardcoded somewhere. In the long term I'd like to get rid of the usr-split,
but that requires some more work.
> Or should we put some binaries in /bin to be consistent with Debian?
> (/bin/ps, /bin/pidof, /usr/bin/top, /usr/bin/vmstat, ... ?)
Just keep them where they are now.
> Btw: This is the commit from procps-ng where they changed it to /bin:
> https://gitlab.com/procps-ng/procps/commit/430b559ba2826f80dffa840622ae0fc744000b13
Michael
--
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
prev parent reply other threads:[~2016-02-11 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:48 Clemens Gruber
2016-02-11 8:30 ` Michael Olbrich [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=20160211083030.GA6633@pengutronix.de \
--to=m.olbrich@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