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 if fixup_perms() has shuffled things around in some random way. I don't think there is any reliable way for fixup_perms() to find and patch all the variables that might refer to paths that it has decided to adjust. Conversely, if FILES is defined in terms of ${base_libdir} and do_install() puts the files there, you can change the value of ${base_libdir} to whatever you like and everything will "just work" without the need for fixup_perms() to move anything. As I mentioned somewhere else in this thread, micro has been using a merged /usr for several years (but done the other way around, so everything is installed into /bin and suchlike) and this has worked just fine without the need for any fsperms magic. I can't see any obvious reason why the new-style /usr merge is fundamentally more difficult. p. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core