From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] e2fsprogs.inc - break shared libs into separate packages
Date: Sun, 02 Jan 2011 18:41:52 +0100 [thread overview]
Message-ID: <ifqdd0$7cl$1@dough.gmane.org> (raw)
In-Reply-To: <4D20968B.4030004@mwester.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02-01-11 16:15, Mike Westerhof wrote:
> Break the two shared libraries (libe2p and libext2fs) out of the general e2fsprogs
> package and into their own packages. This avoids pulling in unwanted executables
> when a distro only desires the basic tools (such as e2fsck and/or mke2fs).
>
> Signed-off-by: Mike Westerhof <mike@mwester.net>
Recipes with e2fsprogs in DEPENDS will need a PR bump as well, since
they might link to these libs as well. This will result in missing
libraries when using package feeds.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNILjgMkyGM64RGpERAl63AJ9d+oy10QAFluRD89/YB6g9ircOuwCfXljo
L2xm9I2E6/rkDke1UFvCG9c=
=Xptt
-----END PGP SIGNATURE-----
next parent reply other threads:[~2011-01-02 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D20968B.4030004@mwester.net>
2011-01-02 17:41 ` Koen Kooi [this message]
2011-01-03 1:03 ` [PATCH] e2fsprogs.inc - break shared libs into separate packages Mike Westerhof
2011-01-03 7:49 ` Koen Kooi
2011-01-04 4:39 ` Mike Westerhof
2011-01-04 8:18 ` Koen Kooi
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='ifqdd0$7cl$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 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.