From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] smartmontools: import from OE classic
Date: Fri, 03 May 2013 15:30:13 +0100 [thread overview]
Message-ID: <2308920.kogFCty2Gp@helios> (raw)
In-Reply-To: <576F47F5-73BA-4369-9A2E-666939097E0A@dominion.thruhere.net>
On Friday 03 May 2013 16:10:40 Koen Kooi wrote:
> Op 27 apr. 2013, om 13:13 heeft Paul Eggleton
<paul.eggleton@linux.intel.com> het volgende geschreven:
> > On Saturday 27 April 2013 06:34:46 Philip Balister wrote:
> >> On 04/27/2013 04:24 AM, Paul Eggleton 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.
>
> Can people raise their hand if they want to have a different version of
> smartmontools in their layer?
Even assuming everyone who could possibly want this is reading this thread,
which is unlikely, in the absence of time machines you won't hear from anyone
who doesn't need it now but does in the future.
As a general rule, people do often want to build versions of recipes from SCM
repositories and having an inc file makes that a bit easier. If we already have
the inc file split I can't see a compelling reason to drop it.
I would also point out that we were asked to preserve these in the original
move to OE-Core and as far as I am aware we have done so.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-03 14:48 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
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 [this message]
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=2308920.kogFCty2Gp@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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.