From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] Style issue for recipes
Date: Thu, 4 Sep 2014 23:03:27 +0800 [thread overview]
Message-ID: <54087F3F.2040103@windriver.com> (raw)
In-Reply-To: <CAJTo0LaRETJdKG-bL+40YtGrVjs4MLVLiydybSUj5ALa2tyxUQ@mail.gmail.com>
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.
// Robert
>
> Specifically I'm looking at the libunwind patch for oe-core (moving
> from meta-oe) which adds libunwind_1.1.bb and libunwind.inc.
> Personally I feel that splitting them up complicates packaging and
> should only be done if there's actually multiple versions being used.
>
> Ross
>
WARNING: multiple messages have this Message-ID (diff)
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Style issue for recipes
Date: Thu, 4 Sep 2014 23:03:27 +0800 [thread overview]
Message-ID: <54087F3F.2040103@windriver.com> (raw)
In-Reply-To: <CAJTo0LaRETJdKG-bL+40YtGrVjs4MLVLiydybSUj5ALa2tyxUQ@mail.gmail.com>
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.
// Robert
>
> Specifically I'm looking at the libunwind patch for oe-core (moving
> from meta-oe) which adds libunwind_1.1.bb and libunwind.inc.
> Personally I feel that splitting them up complicates packaging and
> should only be done if there's actually multiple versions being used.
>
> Ross
>
next prev parent reply other threads:[~2014-09-04 15:03 UTC|newest]
Thread overview: 26+ 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 [this message]
2014-09-04 15:03 ` Robert Yang
2014-09-04 15:29 ` Peter A. Bigot
2014-09-04 15:41 ` [oe] " akuster808
2014-09-04 15:41 ` [OE-core] " akuster808
2014-09-04 16:26 ` [oe] " Burton, Ross
2014-09-04 16:26 ` [OE-core] " Burton, Ross
2014-09-04 20:03 ` [oe] " akuster808
2014-09-04 20:03 ` [OE-core] " akuster808
2014-09-04 16:07 ` [oe] " Enrico Scholz
2014-09-04 16:29 ` Burton, Ross
2014-09-04 16:44 ` Peter A. Bigot
2014-09-04 17:00 ` Enrico Scholz
2014-09-04 17:38 ` Andreas Müller
2014-09-04 18:36 ` Enrico Scholz
2014-09-04 19:12 ` Burton, Ross
2014-09-29 0:51 ` Trevor Woerner
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 ` [oe] " Paul Eggleton
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=54087F3F.2040103@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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.