public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Matthias Schiffer <mschiffer@universe-factory.net>
To: roman@khimov.ru
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: Sun, 10 Jan 2016 19:01:57 +0100	[thread overview]
Message-ID: <56929C95.4020900@universe-factory.net> (raw)
In-Reply-To: <2644403.ISKvOHQyRX@masala.hex>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

On 01/10/2016 06:52 PM, Roman Khimov wrote:
> В письме от 10 января 2016 18:13:03 пользователь Matthias Schiffer написал:
>> * I stand by my opinion that moving files automatically is a bad idea,
> 
> But that's exactly what can make many of /usr merge changes automatically. 
> Take the kernel as an example, you just don't need the first two hunks of the 
> kernel.bbclass patch, fs-perms fixes that for you if it's told that /lib is a 
> symlink to 'usr/lib'.

I can see that it makes things simpler, but I'm more interested in a
correct solution than a simple one.

> 
>> and the FILES issue mentioned in the other thread further backs my point
> 
> IMO, FILES just shouldn't use hard-coded /lib or any other hard-coded path 
> like that.
> 

But if FILES depends on ${base_libdir} etc., the rest of the package
should also be adjusted to install all its files into ${base_libdir}
instead of /lib. Installing files to /lib, but putting ${base_libdir}
into FILES seems extremely broken to me.

Matthias


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-01-10 18: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 [this message]
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=56929C95.4020900@universe-factory.net \
    --to=mschiffer@universe-factory.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=roman@khimov.ru \
    /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