All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] e2fsprogs: fix packaging error for libext2fs
Date: Thu, 10 May 2012 16:08:03 -0500	[thread overview]
Message-ID: <4FAC2E33.7020204@windriver.com> (raw)
In-Reply-To: <CAMKF1sp3RJsrUC5befeKBn+sDQNw2wpUvO2Co+O9eSAhJ5BiLA@mail.gmail.com>

On 5/10/12 3:48 PM, Khem Raj wrote:
> On Thu, May 10, 2012 at 1:40 PM, Mark Hatle<mark.hatle@windriver.com>  wrote:
>> On 5/10/12 3:30 PM, Khem Raj wrote:
>>>
>>> On Thu, May 10, 2012 at 1:03 PM, Andreas Oberritter
>>> <obi@opendreambox.org>    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
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-05-10 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 20:03 [PATCH] e2fsprogs: fix packaging error for libext2fs Andreas Oberritter
2012-05-10 20:30 ` Khem Raj
2012-05-10 20:40   ` Mark Hatle
2012-05-10 20:48     ` Khem Raj
2012-05-10 21:08       ` Mark Hatle [this message]
2012-05-10 21:23         ` Khem Raj
2012-05-10 21:44   ` Andreas Oberritter
2012-05-10 22:02     ` Marko Lindqvist
2012-05-11 17:38 ` Saul Wold

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=4FAC2E33.7020204@windriver.com \
    --to=mark.hatle@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.