On 5/10/12 3:48 PM, Khem Raj wrote:
On Thu, May 10, 2012 at 1:40 PM, Mark Hatle<[email protected]>  wrote:
On 5/10/12 3:30 PM, Khem Raj wrote:

On Thu, May 10, 2012 at 1:03 PM, Andreas Oberritter
<[email protected]>    wrote:


-FILES_libext2fs = "${libdir}/e2initrd_helper ${libdir}/libext2fs.so.*"
+FILES_libext2fs = "${libdir}/e2initrd_helper
${base_libdir}/libext2fs.so.*"


its probably not a good idea to mix files from libdir and base_libdir
in a single
package. Since lately we have been accommodating /usr to be mounted
independently.


I am assuming the e2initrd_helper is an libexec component...  Will

but its being installed into ${libdir}/e2initrd_helper I dont think
libdir will exist initially.

package install/image creation expects the full filesystem to be mounted. It's only during boot that partial mounts may exist.

I don't know what the e2initrd_helper does.. if it's required for booting, then it's needed in /... (or if libext2fs can't run w/o it.)

--Mark

libext2fs.so.* still work (during initial boot) w/o the libexec component?
  (I am assuming it will...)

So this looks correct to me.  The split packages can have mixed base and
prefixed components... it's the filesystem that we hope will work without
the /usr being mounted.  But if the library requires an item in /usr, then
we may have to move that item to /lib as well....

--Mark


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to