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: Tue, 05 Jan 2016 22:04:43 +0000 [thread overview]
Message-ID: <1452031483.2002.104.camel@pbcl.net> (raw)
In-Reply-To: <568AF44A.2040804@universe-factory.net>
On Mon, 2016-01-04 at 23:38 +0100, Matthias Schiffer wrote:
> Of course, the alternative would be to force such distros to
> override the bases-files recipe in a .bbappend.
I don't think this would be an especially big deal. The whole contents
of base-files is already fairly distro-specific and almost any
non-trivial distro is probably going to be either adjusting or replacing
that recipe anyway.
Alternatively, one could argue that these symlinks have nothing much to
do with the rest of base-files and they should go in a completely
separate recipe which the distro could add to IMAGE_INSTALL if it
wished. That might be even better.
p.
next prev parent reply other threads:[~2016-01-05 22:04 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
2016-01-05 22:04 ` Phil Blundell [this message]
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=1452031483.2002.104.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