From: Matthias Schiffer <mschiffer@universe-factory.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib
Date: Tue, 5 Jan 2016 00:46:11 +0100 [thread overview]
Message-ID: <568B0443.5090407@universe-factory.net> (raw)
In-Reply-To: <568AF96A.50302@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
On 01/04/2016 11:59 PM, Mark Hatle wrote:
> On 1/2/16 5:53 PM, Matthias Schiffer wrote:
>> These directories conflict with the symlinks created for merged-usr setups.
>>
>> Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
>> ---
>> v2: create both ${base_libdir} and ${nonarch_base_libdir}
>>
>> meta/recipes-core/base-files/base-files_3.0.14.bb | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb b/meta/recipes-core/base-files/base-files_3.0.14.bb
>> index b71d5c5..2af7ecd 100644
>> --- a/meta/recipes-core/base-files/base-files_3.0.14.bb
>> +++ b/meta/recipes-core/base-files/base-files_3.0.14.bb
>> @@ -33,8 +33,8 @@ INHIBIT_DEFAULT_DEPS = "1"
>> docdir_append = "/${P}"
>> dirs1777 = "/tmp ${localstatedir}/volatile/tmp"
>> dirs2775 = ""
>> -dirs755 = "/bin /boot /dev ${sysconfdir} ${sysconfdir}/default \
>> - ${sysconfdir}/skel /lib /mnt /proc ${ROOT_HOME} /run /sbin \
>> +dirs755 = "${base_bindir} /boot /dev ${sysconfdir} ${sysconfdir}/default \
>> + ${sysconfdir}/skel ${base_libdir} ${nonarch_base_libdir} /mnt /proc ${ROOT_HOME} /run ${base_sbindir} \
>> ${prefix} ${bindir} ${docdir} /usr/games ${includedir} \
>> ${libdir} ${sbindir} ${datadir} \
>> ${datadir}/common-licenses ${datadir}/dict ${infodir} \
>>
>
> I agree this new set looks correct.. but I'd like to see the corresponding
> change to fs-perms that sets the permissions and such for each of these new
> locations.
>
> --Mark
>
The current meta/files/fs-perms.txt doesn't mention any of /bin, /sbin
or /lib, and seemingly never did. I guess they could be added, but that
could also be done in a separate patch (and as I mentioned in another
mail, I'm not exactly a fan of the fs-perms concept, so I don't really
care.)
Matthias
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-01-04 23:46 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 [this message]
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
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=568B0443.5090407@universe-factory.net \
--to=mschiffer@universe-factory.net \
--cc=mark.hatle@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.