From: L A Walsh <lkml@tlinx.org>
To: util-linux@vger.kernel.org
Subject: RFD: --enable-bindir-path ?
Date: Sun, 26 Aug 2018 10:54:49 -0700 [thread overview]
Message-ID: <5B82E969.6090409@tlinx.org> (raw)
Was wondering about the addition of an "enable-bindir-path" which would
only use
paths with /bin instead of /usr/bin for setups where /usr/bin -> /bin
(like cygwin who mounts /bin and /lib on /usr/bin and /usr/lib -- using
mounts instead of symlinks). The've had that since the beginning with
nothing being
installed in /usr/bin or /usr/lib.
Was also wondering why that wasn't chosen as a default for merging, since
/bin and /lib are almost always on the root file system so they are always
there, versus /usr/{bin,lib{,64}} which may need to be mounted before it can
be used...if it can't be mounted, having things in /bin & /lib pointed
to /usr won't work so well.
Anyway, just thought the option would be easy enough apart from other
issues(?).
next reply other threads:[~2018-08-26 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 17:54 L A Walsh [this message]
2018-08-30 8:45 ` RFD: --enable-bindir-path ? Karel Zak
2018-08-31 22:55 ` L A Walsh
2018-09-03 10:17 ` Karel Zak
2018-09-04 9:41 ` Karel Zak
2018-09-07 2:52 ` L A Walsh
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=5B82E969.6090409@tlinx.org \
--to=lkml@tlinx.org \
--cc=util-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).