From: Daiane Angolini <daiane.angolini@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe to u-boot-fsl
Date: Fri, 14 Dec 2012 14:50:07 -0200 [thread overview]
Message-ID: <50CB58BF.5030309@freescale.com> (raw)
In-Reply-To: <CAP9ODKrvxHRCWsLMdD9VLG-5LRJSuzDTw7c_2Ucawn+5J_taxA@mail.gmail.com>
On 12/14/2012 01:33 PM, Otavio Salvador wrote:
>> IMHO renaming the recipe is not the right way to do.
>
> The only two recipes which are in this set are:
>
> u-boot
> linux-mainline
>
> So my proposal is to use:
>
> u-boot-fslc
> linux-fslc
>
> What are people thoughts about it?
I see that we have 2 options.
One of then is the "most right" one - keep the name as is and teach
everyone how to add a bbappend, and PREFERED_PROVIDER and
DEFAULT_PREFERENCE for every single guy caming here because he has a
u-boot recipe in their recipe.
In the other hand, we may rename our u-boot recipe to
u-boot-somethingelse. This way, we have to face less support, and no
need to teach anyone how to fix their layer.
How I'm lazy, I would choose the renaming option.
If I'm wrong on any point, please let me know. I'm not sure I completely
understand the issue here, so I may be simplistic in my interpretation.
Daiane
Daiane
next prev parent reply other threads:[~2012-12-14 16:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 11:57 [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe to u-boot-fsl Andrei Gherzan
2012-12-14 11:57 ` [meta-fsl-arm][PATCH 2/3] u-boot-fsl: This recipe provides u-boot Andrei Gherzan
2012-12-14 11:57 ` [meta-fsl-arm][PATCH 3/3] fsl-default-providers.inc: u-boot recipe was renamed to u-boot-fsl Andrei Gherzan
2012-12-14 12:00 ` [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe " Andrei Gherzan
2012-12-14 12:36 ` Daiane Angolini
2012-12-14 12:41 ` Otavio Salvador
2012-12-14 12:43 ` Andrei Gherzan
2012-12-14 13:20 ` Daiane Angolini
2012-12-14 13:23 ` Andrei Gherzan
2012-12-14 12:56 ` Daiane Angolini
2012-12-14 12:27 ` Daiane Angolini
2012-12-14 13:53 ` Eric Bénard
2012-12-14 13:56 ` Andrei Gherzan
2012-12-14 14:01 ` Eric Bénard
2012-12-14 14:04 ` Andrei Gherzan
2012-12-14 14:13 ` Eric Bénard
[not found] ` <CAK18fxF6VYBTZChgrO_n9PGge8tCWngyFPw=6JD+8sTBMPmeTQ@mail.gmail.com>
2012-12-14 14:26 ` Eric Bénard
2012-12-14 15:14 ` Otavio Salvador
2012-12-14 15:30 ` Eric Bénard
2012-12-14 15:33 ` Otavio Salvador
2012-12-14 16:50 ` Daiane Angolini [this message]
2012-12-14 16:53 ` Otavio Salvador
2012-12-14 17:29 ` Andrei Gherzan
2012-12-14 17:52 ` Otavio Salvador
2012-12-14 17:58 ` Eric Bénard
2012-12-14 18:12 ` Otavio Salvador
2012-12-14 18:22 ` Eric Bénard
[not found] ` <CA+jg_OWZpR7iazC=anVXbFFbzm8jV5O-f1ZwOoTuC3a3j-kzTA@mail.gmail.com>
2012-12-14 23:08 ` Daiane Angolini
2012-12-14 23:11 ` Andrei Gherzan
2012-12-14 23:20 ` Eric Bénard
2012-12-15 16:04 ` Otavio Salvador
2012-12-15 18:18 ` Eric Bénard
2012-12-15 18:33 ` Otavio Salvador
2012-12-15 20:43 ` Andrei Gherzan
2012-12-16 14:30 ` Daiane Angolini
2012-12-16 17:06 ` Otavio Salvador
2012-12-19 19:35 ` McClintock Matthew-B29882
2012-12-19 19:40 ` Otavio Salvador
2012-12-19 19:46 ` McClintock Matthew-B29882
2012-12-19 19:54 ` Otavio Salvador
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=50CB58BF.5030309@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.