Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr
Date: Wed, 2 Sep 2015 15:07:57 +0100	[thread overview]
Message-ID: <55E702BD.5090608@imgtec.com> (raw)
In-Reply-To: <20150902160446.7fbf9ef6@free-electrons.com>

Dear Thomas Petazzoni,

On 09/02/2015 03:04 PM, Thomas Petazzoni wrote:
> Dear Mike Williams,
> 
> On Wed, 2 Sep 2015 09:50:34 -0400, Mike Williams wrote:
> 
>> It's not just what systemd expects, many packages by default install their
>> systemd-related items to /lib, etc. instead of /usr/lib, so we either have
>> manual fixes to the .mk files for those packages or inconsistencies in
>> where those items go. As an example, I believe rsyslog is passed a special
>> flag setting its systemd install location to /usr/lib, and gpsd is still
>> just installing to /lib/systemd/system.
>>
>> It wouldn't surprise me if most of our systemd users had already merged
>> their directories in their skeleton; I will probably do so soon as well.
> 
> Hum, right, I see. Then maybe Yann's patch is the right answer. In fact
> what I'd like to see in Buildroot is a group of people taking care of
> the systemd-related issues. So if you're willing (with others) to
> tackle that, it would be very useful. If you agree with Yann's patch,
> can you please test it and give your formal Tested-by/Reviewed-by?
> 
> Thanks,
> 
> Thomas
> 

and what about also selecting BR2_ROOTFS_USR_SYMLINKS in systemd's
Config.in?

Regards,

Vincent.

  parent reply	other threads:[~2015-09-02 14:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 22:55 [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-09-03 23:47 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
2015-09-14 21:32         ` Thomas Petazzoni

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=55E702BD.5090608@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --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