From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [PATCH] util-linux-ng: Do not provide libblkid.
Date: Fri, 17 Jul 2009 01:26:10 -0700 [thread overview]
Message-ID: <20090717082610.GC24991@gmail.com> (raw)
In-Reply-To: <h3p932$3g5$1@ger.gmane.org>
On (17/07/09 09:26), Koen Kooi wrote:
> On 16-07-09 23:31, Khem Raj wrote:
>> Currently we let utils-linux-ng provide
>> libblkid package which then ends up being
>> provided twice once from e2fsprogs-libs and
>> once from util-linux-ng. Future versions might
>> move libblkid and libuuid to utils-linux-ng
>> till then we will use e2fsprogs-libs provided one
>> on the system
>>
>> Signed-off-by: Khem Raj<raj.khem@gmail.com>
>
> NAK!!!! We need the new blkid for udev and friends, so you'll break
> angstrom with this changes. The right way is to kill the e2fsprogs one.
>
I thought of doing this switch once util-linux-ng 2.16 is released(15th july it was) then
this library would come from util-linux-ng for older ones let it
come from e2fsprogs-libs. It seems udev angstrom is using is quite latest. Anyway current
util-linux-ng recipes are broken too because they ask for this
library to be provided for all versions but it only appeared in
2.15 for first time.
so I think we wont be able to use any combination of util-linux-ng
and e2fsprogs-libs.
if a distro is using util-linux-ng older than 2.15 (nothing found in conf/ ) then it has to
get this library from e2fsprogs-libs. It there a way to say that in recipes or bitbake magic ?
If this looks viable that all distros use latest util-linux-ng
then we can stop providing it from e2fsprogs-libs,
if someone wanted to use utils-linux-ng < 2.15 then he gets no libblkid
opinions ?
Thx
-Khem
next prev parent reply other threads:[~2009-07-17 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 21:31 [PATCH] util-linux-ng: Do not provide libblkid Khem Raj
2009-07-16 23:28 ` Denys Dmytriyenko
2009-07-17 7:26 ` Koen Kooi
2009-07-17 8:26 ` Khem Raj [this message]
2009-07-19 16:50 ` Khem Raj
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=20090717082610.GC24991@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.