Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-11 Thread Mark Hatle
On 1/10/16 11:13 AM, Matthias Schiffer wrote: (Trimming to just this comment) > * I stand by my opinion that moving files automatically is a bad idea, > and the FILES issue mentioned in the other thread further backs my point > (besides that issue, I've mentioned relative symlinks and relative

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-10 Thread Roman Khimov
В письме от 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

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-10 Thread Matthias Schiffer
On 01/05/2016 01:16 AM, Mark Hatle wrote: > On 1/4/16 5:46 PM, Matthias Schiffer wrote: >> 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

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-10 Thread Matthias Schiffer
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

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-10 Thread Phil Blundell
On Sun, 2016-01-10 at 20:52 +0300, Roman Khimov wrote: > IMO, FILES just shouldn't use hard-coded /lib or any other hard-coded path > like that. Well, right, but that doesn't really address the issue. Even if FILES is defined in terms of ${base_libdir} or whatever, it's still not going to match

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-04 Thread Mark Hatle
On 1/4/16 5:46 PM, Matthias Schiffer wrote: > 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 >>> ---

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-04 Thread Matthias Schiffer
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 >> --- >> v2: create both ${base_libdir} and

Re: [OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-04 Thread Mark Hatle
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 > --- > v2: create both ${base_libdir} and ${nonarch_base_libdir} > >

[OE-core] [PATCH v2 2/3] base-files: create ${base_bindir} etc. instead of /bin, /sbin and /lib

2016-01-02 Thread Matthias Schiffer
These directories conflict with the symlinks created for merged-usr setups. Signed-off-by: Matthias Schiffer --- 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