Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/2] unique -dev package
Date: Tue, 07 Apr 2015 16:04:04 +0100	[thread overview]
Message-ID: <1428419044.14020.470.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1428410929.git.liezhi.yang@windriver.com>

On Tue, 2015-04-07 at 05:58 -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
> 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

I'd much prefer that ${PN}-dev was the dev package rather than the way
round that this patch series has things...

Cheers,

Richard



  parent reply	other threads:[~2015-04-07 15:04 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 ` Richard Purdie [this message]
2016-04-10 22:51 ` [RFC PATCH 0/2] unique -dev package 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=1428419044.14020.470.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox