From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr
Date: Wed, 7 Oct 2015 23:03:58 +0100 [thread overview]
Message-ID: <561596CE.9080502@mind.be> (raw)
In-Reply-To: <CANPyyuP3SBaEfR68jL=OqQqfkLov=1GLjW-r05CsOQgEOHY=Fg@mail.gmail.com>
On 07-10-15 17:19, Mike Williams wrote:
> All,
>
> > However, I'm not really in favour of it. I don't see that it brings
> > a lot of benefit, other than reducing the number of symlinks from 3
> > to 1. But it does create /share and /local which looks weird could
> > potentially conflict with existing user directories (e.g. a
> > mountpoint for windows shares...). Also it makes it more complicated
> > for the user to implement a fedora-like mounted /usr.
>
> Ok - fine, having 1 or 3 symlinks isn't really a big deal. Just symlinking /usr
> seemed the simplest possible solution.
>
>
> Any reason this wasn't committed? Just reviewing my list of out-of-tree patches...
Because it is a non-trivial change, and we don't have runtime testing to give
Peter sufficient trust to just commit it, so he will want to look at the patch
in detail before committing. And by now it got snowed under by other patches...
So it's good that you push for it ;-).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-07 22:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 23:47 [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr Yann E. MORIN
2015-09-04 7:48 ` Vicente Olivert Riera
2015-09-04 8:16 ` Arnout Vandecappelle
2015-09-04 16:29 ` Yann E. MORIN
2015-09-04 19:05 ` Arnout Vandecappelle
2015-09-04 16:12 ` Yann E. MORIN
2015-09-04 8:11 ` Thomas Petazzoni
2015-09-04 8:19 ` Arnout Vandecappelle
2015-09-04 16:31 ` Yann E. MORIN
2015-09-14 21:12 ` Peter Korsgaard
2015-09-14 21:23 ` Yann E. MORIN
2015-09-14 21:26 ` Arnout Vandecappelle
2015-09-14 21:39 ` Peter Korsgaard
2015-10-07 16:19 ` Mike Williams
2015-10-07 22:03 ` Arnout Vandecappelle [this message]
2015-09-14 21:32 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2015-09-01 22:55 Yann E. MORIN
2015-09-02 4:54 ` Baruch Siach
2015-09-02 7:10 ` Thomas Petazzoni
2015-09-02 13:50 ` Mike Williams
2015-09-02 14:04 ` Thomas Petazzoni
2015-09-02 14:05 ` Mike Williams
2015-09-02 14:28 ` Yann E. MORIN
2015-09-02 14:07 ` Vicente Olivert Riera
2015-09-02 14:11 ` Yann E. MORIN
2015-09-02 14:12 ` Thomas Petazzoni
2015-09-02 14:13 ` Vicente Olivert Riera
2015-09-02 20:59 ` Arnout Vandecappelle
2015-09-02 21:17 ` Arnout Vandecappelle
2015-09-02 22:09 ` Yann E. MORIN
2015-09-03 14:46 ` Mike Williams
2015-09-03 15:12 ` Vicente Olivert Riera
2015-09-03 15:57 ` Yann E. MORIN
2015-09-02 22:07 ` Yann E. MORIN
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=561596CE.9080502@mind.be \
--to=arnout@mind.be \
--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