From: Robert Yang <liezhi.yang@windriver.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/2] unique -dev package
Date: Mon, 11 Apr 2016 09:19:32 +0800 [thread overview]
Message-ID: <570AFBA4.40201@windriver.com> (raw)
In-Reply-To: <20160410225130.GK16135@denix.org>
On 04/11/2016 06:51 AM, Denys Dmytriyenko wrote:
> On Tue, Apr 07, 2015 at 05:58:13AM -0700, Robert Yang wrote:
>> 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
>
> I know it is already 1 year since this change. But I can't seem to find any
> discussion or any explanation to why this change was required and what
> specific problem it was supposed to fix. Please point me to a clear reasoning
> of this change. Thanks.
There is only one source package, so there should be only one pack of header
files, dev libs, and so on, and they should be placed in a uniq pkg.
// Robert
>
next prev parent reply other threads:[~2016-04-11 1:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:58 [RFC PATCH 0/2] unique -dev package Robert Yang
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 [this message]
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=570AFBA4.40201@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=denis@denix.org \
--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.