Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] e2fsprogs: fix packaging error for libext2fs
Date: Thu, 10 May 2012 23:44:58 +0200	[thread overview]
Message-ID: <4FAC36DA.8080201@opendreambox.org> (raw)
In-Reply-To: <CAMKF1spfSiBy0F-cP7Q2NYT2dg2CFqvfXxuxR_=-F2o8gdBwGw@mail.gmail.com>

On 10.05.2012 22:30, 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 have no idea what e2initrd_helper does, but this can still be
addressed in a later patch.

Currently, libext2fs.so.* gets packaged into the "e2fsprogs" package,
which is worse than your concerns, because it drags many unneeded
dependencies into the image.

FWIW, e2initrd_helper doesn't seem to be required during a usual boot
process, as nobody seems to have missed it. At least no automatic
dependencies on the libext2fs package were generated before this patch.

Regards,
Andreas



  parent reply	other threads:[~2012-05-10 21:54 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
2012-05-10 21:23         ` Khem Raj
2012-05-10 21:44   ` Andreas Oberritter [this message]
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=4FAC36DA.8080201@opendreambox.org \
    --to=obi@opendreambox.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox