From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BEE02E00294 for ; Fri, 14 Dec 2012 08:48:18 -0800 (PST) Received: from mail134-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 16:48:17 +0000 Received: from mail134-tx2 (localhost [127.0.0.1]) by mail134-tx2-R.bigfish.com (Postfix) with ESMTP id CFC744A039D; Fri, 14 Dec 2012 16:48:17 +0000 (UTC) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI X-SpamScore: -9 X-BigFish: VS-9(zzbb2dI98dI9371I1432I1455Mzz1de0h1202h1e76h1d1ah1d2ahzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h) Received: from mail134-tx2 (localhost.localdomain [127.0.0.1]) by mail134-tx2 (MessageSwitch) id 1355503695279852_10007; Fri, 14 Dec 2012 16:48:15 +0000 (UTC) Received: from TX2EHSMHS022.bigfish.com (unknown [10.9.14.236]) by mail134-tx2.bigfish.com (Postfix) with ESMTP id 3D8F81C017F; Fri, 14 Dec 2012 16:48:15 +0000 (UTC) Received: from mail.freescale.net (70.37.183.190) by TX2EHSMHS022.bigfish.com (10.9.99.122) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 16:48:13 +0000 Received: from az84smr01.freescale.net (10.64.34.197) by 039-SN1MMR1-004.039d.mgd.msft.net (10.84.1.14) with Microsoft SMTP Server (TLS) id 14.2.318.3; Fri, 14 Dec 2012 16:48:13 +0000 Received: from [10.29.244.61] ([10.29.244.61]) by az84smr01.freescale.net (8.14.3/8.14.0) with ESMTP id qBEGmAur011356; Fri, 14 Dec 2012 09:48:11 -0700 Message-ID: <50CB58BF.5030309@freescale.com> Date: Fri, 14 Dec 2012 14:50:07 -0200 From: Daiane Angolini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Otavio Salvador References: <1355486234-7035-1-git-send-email-andrei.gherzan@windriver.com> <20121214145331.54c07822@eb-e6520> <20121214150150.1aa8eaf5@eb-e6520> <20121214151314.001f1ec8@eb-e6520> <20121214152619.79098454@eb-e6520> <20121214163024.7427cf1d@eb-e6520> In-Reply-To: X-OriginatorOrg: freescale.com Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe to u-boot-fsl X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2012 16:48:19 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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