Poky Project Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, poky@yoctoproject.org
Subject: Re: [PATCH 0/3] util-linux: split out libuuid and libblkid
Date: Wed, 19 Jan 2011 14:03:28 -0600	[thread overview]
Message-ID: <4D374390.5040500@windriver.com> (raw)
In-Reply-To: <20F0A899-BE2B-4743-B435-7B9C64AD501C@dominion.thruhere.net>

On 1/19/11 1:51 PM, Koen Kooi wrote:
> Tangent: have you considered switching to util-linux-ng?
> 
> Op 19 jan 2011, om 17:55 heeft Paul Eggleton het volgende geschreven:
> 
>> Split libuuid and libblkid from util-linux into separate runtime packages.
>> Slightly reduces the overall footprint of other packages that depend on these 
>> libraries.

The util-linux-ng components are licensed GPLv3, so they could be alternatives,
but we need a GPLv2 version of the components for some systems.

--Mark

>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>>  Branch: paule/util-linux-libsplit
>>  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/util-linux-libsplit
>>
>> Thanks,
>>    Paul Eggleton <paul.eggleton@linux.intel.com>
>> ---
>>
>>
>> Paul Eggleton (3):
>>  util-linux: split out libuuid and libblkid into separate packages
>>  gst-plugins-base: add util-linux to DEPENDS
>>  Bump PR on recipes that depend on util-linux
>>
>> .../nfs-utils/nfs-utils_1.2.3.bb                   |    2 +-
>> meta/recipes-core/util-linux/util-linux.inc        |    6 ++++--
>> meta/recipes-core/util-linux/util-linux_2.17.2.bb  |    2 +-
>> .../e2fsprogs/e2fsprogs_1.41.12.bb                 |    2 +-
>> meta/recipes-devtools/mtd/mtd-utils_1.4.1.bb       |    2 +-
>> meta/recipes-graphics/xorg-lib/libsm_1.2.0.bb      |    2 +-
>> .../gstreamer/gst-plugins-base_0.10.31.bb          |    4 ++--
>> 7 files changed, 11 insertions(+), 9 deletions(-)
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
> 
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2011-01-19 20:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 16:55 [PATCH 0/3] util-linux: split out libuuid and libblkid Paul Eggleton
2011-01-19 16:55 ` [PATCH 1/3] util-linux: split out libuuid and libblkid into separate packages Paul Eggleton
2011-01-19 19:13   ` Saul Wold
2011-01-20 10:15     ` Paul Eggleton
2011-01-21  3:15       ` Qing He
2011-01-19 16:55 ` [PATCH 2/3] gst-plugins-base: add util-linux to DEPENDS Paul Eggleton
2011-01-19 16:55 ` [PATCH 3/3] Bump PR on recipes that depend on util-linux Paul Eggleton
2011-01-19 19:51 ` [PATCH 0/3] util-linux: split out libuuid and libblkid Koen Kooi
2011-01-19 20:03   ` Mark Hatle [this message]
2011-01-19 21:24     ` Richard Purdie
2011-01-19 21:33       ` Mark Hatle
2011-01-19 21:50         ` Richard Purdie
2011-01-21  3:33           ` Qing He
2011-01-19 20:05   ` Bruce Ashfield
2011-01-19 20:06   ` Richard Purdie
2011-01-21  3:24   ` Qing He

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=4D374390.5040500@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.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