From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Removal of e2fsprogs-libs
Date: Tue, 23 Mar 2010 20:41:54 +0100 [thread overview]
Message-ID: <hob5i2$t26$1@dough.gmane.org> (raw)
In-Reply-To: <20100323183615.GE3249@xora-eee.xora.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-03-10 19:36, Graeme Gregory wrote:
> On Tue, Mar 23, 2010 at 07:01:23PM +0100, Marcin Juszkiewicz wrote:
>>
>> During last days I spent a bit of time on e2fsprogs* and util-linux-ng
>> recipes. They are cleaner now but there is still some work to do.
>>
>> We have many recipes which depends on 'e2fsprogs-libs' when they want
>> 'libblkid' or 'libuuid' which are provided by 'e2fsprogs-libs' and
>> 'util-linux-ng' recipes. I checked how Debian solves that and got into point
>> where there is no 'e2fsprogs-libs' recipes in my tree and everything is
>> building.
>>
>> What needs to be changed?
>>
>> 1. git rm -r recipes/e2fsprogs-libs
>> 2. check each recipe which depends on 'e2fsprogs-libs' which library it really
>> wants
>> 3. change each recipe which wants 'libblkid' or 'libuuid' to depend on
>> 'util-linux-ng'
>> 4. change each recipe which wants 'libcom_err' or 'libss' to depend on
>> 'e2fsprogs'
>> 5. add "--with-elf-shlibs" to 'e2fsprogs' to get 'libcom_err' and 'libss'
>> 6. fix packaging of 'e2fsprogs' to get separate packages for libraries.
>>
>> I can work on that in next days but want to inform everyone that such change
>> will be done.
>>
> Hrw thanks for cleaning this up, feel free to add my ack to your completed
> worked.
And mine as well. Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLqRmCMkyGM64RGpERAi61AJ0TiULvauZGkFG+leI7aLr1U/of9QCghkTb
n7P2S1GSXnTbgLlXZ78UM9E=
=xl6V
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-23 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:01 [RFC] Removal of e2fsprogs-libs Marcin Juszkiewicz
2010-03-23 18:36 ` Graeme Gregory
2010-03-23 19:41 ` Koen Kooi [this message]
2010-03-24 7:32 ` Frans Meulenbroeks
2010-03-24 16:35 ` 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='hob5i2$t26$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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