From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Removal of e2fsprogs-libs
Date: Tue, 23 Mar 2010 19:01:23 +0100 [thread overview]
Message-ID: <201003231901.24017.marcin@juszkiewicz.com.pl> (raw)
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.
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next reply other threads:[~2010-03-23 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:01 Marcin Juszkiewicz [this message]
2010-03-23 18:36 ` [RFC] Removal of e2fsprogs-libs Graeme Gregory
2010-03-23 19:41 ` Koen Kooi
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=201003231901.24017.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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 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.