From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Style issue for recipes
Date: Thu, 04 Sep 2014 10:29:46 -0500 [thread overview]
Message-ID: <5408856A.5080806@pabigot.com> (raw)
In-Reply-To: <54087F3F.2040103@windriver.com>
On 09/04/2014 10:03 AM, Robert Yang wrote:
>
> On 09/04/2014 10:12 PM, Burton, Ross wrote:
>> Hi,
>>
>> Quick question of style for the community to bikeshed on: in the
>> general case should recipes be split into foo_1.2.bb and foo.inc, or
>> should they only split to bb/inc if there are multiple versions and
>> generally there should just be foo_1.2.bb.
>
> I think that put the constants in .inc is helpful for upgrading, for
> example, the SUMMARY, DESCRIPTION, HOMEPAGE, SECTION, inherit and so on,
> they are unlikely to change when upgrade.
I believe most of those carry over when an upgrade is simply a matter of
renaming the recipe from foo_1.2.bb to foo_3.4.bb and changing the
checksums. I don't think foo.inc is warranted when only one file will
ever include it.
I agree libunwind is a perfect example of where they can be merged into
one file to simplify things, as long as everybody remembers to use -M
when generating the patch.
Peter
next prev parent reply other threads:[~2014-09-04 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 14:12 Style issue for recipes Burton, Ross
2014-09-04 15:03 ` Robert Yang
2014-09-04 15:29 ` Peter A. Bigot [this message]
2014-09-04 15:41 ` [OE-core] " akuster808
2014-09-04 16:26 ` Burton, Ross
2014-09-04 20:03 ` akuster808
2014-09-04 16:34 ` Burton, Ross
2014-09-04 17:29 ` Andreas Müller
2014-09-04 17:54 ` Philip Balister
2014-09-04 19:10 ` Burton, Ross
2014-09-05 13:58 ` Mike Looijmans
2014-09-05 16:13 ` Burton, Ross
2014-09-05 9:11 ` Paul Eggleton
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=5408856A.5080806@pabigot.com \
--to=pab@pabigot.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox