From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [ptxdist] executables in /usr/bin vs /bin
Date: Wed, 10 Feb 2016 18:48:04 +0100 [thread overview]
Message-ID: <20160210174804.GA9521@archie.tuxnet.lan> (raw)
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)
Or should we put some binaries in /bin to be consistent with Debian?
(/bin/ps, /bin/pidof, /usr/bin/top, /usr/bin/vmstat, ... ?)
Btw: This is the commit from procps-ng where they changed it to /bin:
https://gitlab.com/procps-ng/procps/commit/430b559ba2826f80dffa840622ae0fc744000b13
Thanks,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-02-10 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:48 Clemens Gruber [this message]
2016-02-11 8:30 ` Michael Olbrich
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=20160210174804.GA9521@archie.tuxnet.lan \
--to=clemens.gruber@pqgruber.com \
--cc=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