From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [RFC PATCH 0/2] unique -dev package
Date: Tue, 7 Apr 2015 05:58:13 -0700 [thread overview]
Message-ID: <cover.1428410929.git.liezhi.yang@windriver.com> (raw)
Hello,
I think that one recipe should only have one -dev package, I'm not sure
whether this is right or not, please feel free to give your comments, we
still have about 30 recipes in oe-core which have more than one dev
packages, more info:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7481
// Robert
The following changes since commit fbaddd724855a829698d853a70eee86118d6a5e7:
package_manager: call createrepo with --dbpath pointing inside WORKDIR (2015-04-02 12:00:55 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/dev
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/dev
Robert Yang (2):
xz: remove xz-dev from PACKAGES
bzip2: remove bzip2-dev from PACKAGES
meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 3 ++-
meta/recipes-extended/xz/xz_5.2.0.bb | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-04-07 12:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:58 Robert Yang [this message]
2015-04-07 12:58 ` [RFC PATCH 1/2] xz: remove xz-dev from PACKAGES Robert Yang
2015-04-07 12:58 ` [RFC PATCH 2/2] bzip2: remove bzip2-dev " Robert Yang
2015-04-08 1:34 ` Khem Raj
2015-04-08 1:55 ` Robert Yang
2015-04-08 2:10 ` Khem Raj
2015-04-08 2:14 ` Robert Yang
2015-04-07 15:04 ` [RFC PATCH 0/2] unique -dev package Richard Purdie
2016-04-10 22:51 ` Denys Dmytriyenko
2016-04-11 1:19 ` Robert Yang
2016-04-11 1:49 ` Denys Dmytriyenko
2016-04-11 8:35 ` Richard Purdie
2016-04-11 13:42 ` Denys Dmytriyenko
2016-04-11 14:12 ` Gary Thomas
2016-04-11 19:10 ` Denys Dmytriyenko
2016-04-11 19:40 ` Burton, Ross
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=cover.1428410929.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@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.