All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] smartmontools: import from OE classic
Date: Fri, 03 May 2013 15:35:04 +0100	[thread overview]
Message-ID: <12323341.7tMrSLVFbj@helios> (raw)
In-Reply-To: <CAP71WjxM+5h436zjUYUAAvO3awMOiyqS1Wo62ibTGQZEmPRiEQ@mail.gmail.com>

On Friday 03 May 2013 16:00:13 Nicolas Dechesne wrote:
> On Mon, Apr 29, 2013 at 8:40 AM, Nicolas Dechesne
> 
> <nicolas.dechesne@linaro.org> wrote:
> > On Sat, Apr 27, 2013 at 1:13 PM, Paul Eggleton
> > 
> > <paul.eggleton@linux.intel.com> wrote:
> >>> > On Friday 26 April 2013 23:41:38 Koen Kooi wrote:
> >>> >> And do you really need a .inc?
> >>> > 
> >>> > Are we removing inc files if they were present in OE Classic? First
> >>> > I've
> >>> > heard if we are...
> >>> 
> >>> If we are trying to reduce the number of versions of recipes we carry,
> >>> dropping .inc files would seem to be a good idea. I don't have strong
> >>> feelings, but it seems like something we should consider.
> >> 
> >> I agree we should try to keep only one version of each recipe in software
> >> layers, however I figure it makes it easier for people to carry their own
> >> versions of recipes in distro layers (particularly older, which may be
> >> required in certain circumstances) if we do keep inc files where they
> >> already exist.
> > 
> > I put the .inc in this patch, indeed because it was there in OE
> > Classic. I can update the patch if there is a consensus to remove the
> > .inc.
> > 
> > also for the INC_PR, I added it, because I thought it makes sense for
> > .bb with .inc to have that. again, i can update the patch if you
> > recommend doing this way.
> 
> hi, can you please let me know what I should do here? i can update the
> patch if needed, but not sure there is a clear consensus on what to
> do!

IMO, let's keep the separate inc file, but drop PR and INC_PR.

Cheers,
Paul


-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-05-03 14:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 20:39 [meta-oe][PATCH] smartmontools: import from OE classic Nicolas Dechesne
2013-04-26 21:41 ` Koen Kooi
2013-04-27  8:24   ` Paul Eggleton
2013-04-27 10:34     ` Philip Balister
2013-04-27 11:13       ` Paul Eggleton
2013-04-29  6:40         ` Nicolas Dechesne
2013-05-03 14:00           ` Nicolas Dechesne
2013-05-03 14:35             ` Paul Eggleton [this message]
2013-05-03 14:40               ` Koen Kooi
2013-05-03 14:48                 ` Paul Eggleton
2013-05-03 14:10         ` Koen Kooi
2013-05-03 14:30           ` Paul Eggleton
2013-05-03 14:39             ` Koen Kooi
2013-05-03 14:30           ` Nicolas Dechesne
2013-05-03 14:42             ` Paul Eggleton
2013-05-03 15:09               ` Martin Jansa
2013-05-03 15:15                 ` Philip Balister
2013-05-06  8:19                   ` Nicolas Dechesne

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=12323341.7tMrSLVFbj@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=nicolas.dechesne@linaro.org \
    --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.