From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] util-linux: bump version to util-linux-ng 2.18
Date: Sun, 05 Dec 2010 21:54:30 +0100 [thread overview]
Message-ID: <4CFBFC06.40800@googlemail.com> (raw)
In-Reply-To: <20101205212409.114c5be8@surf>
Am 05.12.2010 21:24, schrieb Thomas Petazzoni:
>
> Yes, I was going to tell Heiko about your previous work. I remember
> that one thing made it a bit complicated to review: the relationship
> with libuuid. I'll try to have a look at the patches again and see if I
> can get them merged.
>
Just for information: Libuuid's origin is within the e2fsprogs package.
Since util-linux-ng 2.16? it is also part of that package. I guess the
goal is to remove libuuid from e2fsprogs and maintain it in ulng.
Recently, both packages provide a plausible libuuid. Both can be used.
Since many emebedded developers will always use busybox (which provides
blkid - 3rd? fork of beside e2fsprogs and ulng?) it may be better to
provide libuuid by e2fsprogs - so you do not need to select another
package.
If the devleopment goes on, ulng might become the leading
implementation. So this version should be selectable, too.
Using both versions at the same time does not look reasonable to me.
Regards,
Ossy
prev parent reply other threads:[~2010-12-05 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 15:00 [Buildroot] [PATCH] util-linux: bump version to util-linux-ng 2.18 heiko at zuerker.org
2010-12-05 20:17 ` Marcus Osdoba
2010-12-05 20:24 ` Thomas Petazzoni
2010-12-05 20:42 ` Heiko Zuerker
2010-12-05 20:54 ` Marcus Osdoba [this message]
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=4CFBFC06.40800@googlemail.com \
--to=marcus.osdoba@googlemail.com \
--cc=buildroot@busybox.net \
/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