From: Matthias Schiffer <mschiffer@universe-factory.net>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 3/3] base-files: create typical merged /usr symlinks if the "merged-usr" distro feature is set
Date: Mon, 4 Jan 2016 23:38:02 +0100 [thread overview]
Message-ID: <568AF44A.2040804@universe-factory.net> (raw)
In-Reply-To: <1451826066.2002.96.camel@pbcl.net>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On 01/03/2016 02:01 PM, Phil Blundell wrote:
> On Sun, 2016-01-03 at 00:53 +0100, Matthias Schiffer wrote:
>> +PACKAGECONFIG ??= " \
>> + ${@bb.utils.contains('DISTRO_FEATURES', 'merged-usr','merged-usr', '', d)} \
>
> Why is this DISTRO_FEATURE (or the corresponding PACKAGECONFIG)
> required? Surely it ought to suffice to simply set ${base_bindir} etc,
> and everything else should follow from that. This, albeit the other way
> around, is what micro has been doing for years.
>
> p.
>
>
Basically, I didn't want to break existing configurations. There might
be unusual distros which don't want these symlinks (or want different
ones). Of course, the alternative would be to force such distros to
override the bases-files recipe in a .bbappend.
I don't know of any OE-based distros with such unusual setups, but
Debian is an example: they basically set base_libdir to /lib/$TARGET,
but don't symlink /lib64 to this on 64bit targets. Instead, /lib64 is
empty except of a symlink to the dynamic linker which is expected in /lib64.
Matthias
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-01-04 22:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 23:52 [PATCH v2 1/3] kernel: allow kernel module and firmware installation with ${nonarch_base_libdir} != "/lib" Matthias Schiffer
2016-01-02 23:53 ` [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib Matthias Schiffer
2016-01-04 22:59 ` Mark Hatle
2016-01-04 23:46 ` Matthias Schiffer
2016-01-05 0:16 ` Mark Hatle
2016-01-10 17:13 ` Matthias Schiffer
2016-01-10 17:52 ` Roman Khimov
2016-01-10 18:01 ` Matthias Schiffer
2016-01-10 22:18 ` Phil Blundell
2016-01-11 15:00 ` Mark Hatle
2016-01-02 23:53 ` [PATCH v2 3/3] base-files: create typical merged /usr symlinks if the "merged-usr" distro feature is set Matthias Schiffer
2016-01-03 13:01 ` Phil Blundell
2016-01-04 22:38 ` Matthias Schiffer [this message]
2016-01-05 22:04 ` Phil Blundell
2016-01-04 22:59 ` Mark Hatle
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=568AF44A.2040804@universe-factory.net \
--to=mschiffer@universe-factory.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.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