From: Phil Blundell <pb@pbcl.net>
To: Matthias Schiffer <mschiffer@universe-factory.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: Sun, 03 Jan 2016 13:01:06 +0000 [thread overview]
Message-ID: <1451826066.2002.96.camel@pbcl.net> (raw)
In-Reply-To: <7ef127138c4ba5c89b42b892c84aaa7766f78a4c.1451778497.git.mschiffer@universe-factory.net>
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.
next prev parent reply other threads:[~2016-01-03 13:01 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 [this message]
2016-01-04 22:38 ` Matthias Schiffer
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=1451826066.2002.96.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=mschiffer@universe-factory.net \
--cc=openembedded-core@lists.openembedded.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