Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Roman Khimov <roman@khimov.ru>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] base-files: create typical merged /usr symlinks if the "merged-usr" distro feature is set
Date: Thu, 17 Dec 2015 14:49:13 +0300	[thread overview]
Message-ID: <20429947.OAhnyEDPKl@bancha.hex> (raw)
In-Reply-To: <567284B0.4020603@universe-factory.net>

В письме от 17 декабря 2015 10:47:28 пользователь Matthias Schiffer написал:
> On 12/16/2015 08:46 PM, Roman Khimov wrote:
> > В письме от 16 декабря 2015 19:12:00 пользователь Matthias Schiffer 
> > написал:
> > Also, you probably want to add this symlinks to fs-perms.txt. I don't
> > quite
> > remember which packages failed for me without it, but there were some.
> 
> Is it even possible to have fs-perms.txt entries depending on a
> DISTRO_FEATURE? 

Probably not.

> And can fs-perms.txt move files from one directory to
> another (as you suggested in your reply for PATCH 2)?

IIRC, yes.

> AFAICT, fs-perms.txt is only there to fix some common issues with
> directory permissions. Most packages already respect base_libdir etc.
> just fine, so in my opinion it would be preferable to just fix the
> packages which don't if adding such things to fs-perms.txt is non-trivial.

fs-perms can fix things automatically, with no additional code in recipes (and 
that's a nice thing IMO), but, yes, at the moment it probably can't do or 
don't do things based on DISTRO_FEATURE settings. Maybe using 
FILESYSTEM_PERMS_TABLES can help or even generating fs-perms on the fly taking 
into account real ${somedir} values.


      reply	other threads:[~2015-12-17 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 18:11 [PATCH 0/4] Implement merged /usr Matthias Schiffer
2015-12-16 18:11 ` [PATCH 1/4] busybox: generalize recipe to work with arbitrary install directories Matthias Schiffer
2015-12-16 18:11 ` [PATCH 2/4] kernel: allow kernel module and firmware installation with ${base_libdir} != "/lib" Matthias Schiffer
2015-12-16 19:48   ` Roman Khimov
2015-12-16 19:49   ` Roman Khimov
2015-12-16 18:11 ` [PATCH 3/4] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib Matthias Schiffer
2015-12-22 17:31   ` Burton, Ross
2015-12-22 18:43     ` Matthias Schiffer
2015-12-22 21:11       ` Burton, Ross
2015-12-16 18:12 ` [PATCH 4/4] base-files: create typical merged /usr symlinks if the "merged-usr" distro feature is set Matthias Schiffer
2015-12-16 19:46   ` Roman Khimov
2015-12-17  9:47     ` Matthias Schiffer
2015-12-17 11:49       ` Roman Khimov [this message]

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=20429947.OAhnyEDPKl@bancha.hex \
    --to=roman@khimov.ru \
    --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