[meta-freescale] [meta-fsl-ppc master] remove DSTRO string from PR due to meta-fsl-ppc is not distro specific

Matthew McClintock msm-oss at mcclintock.net
Sun Mar 3 08:51:57 PST 2013

On Fri, Mar 1, 2013 at 6:00 AM, Otavio Salvador <otavio at ossystems.com.br> wrote:
> On Fri, Mar 1, 2013 at 3:06 AM, McClintock Matthew-B29882
> <B29882 at freescale.com> wrote:
>> On Thu, Feb 28, 2013 at 6:35 AM, Otavio Salvador
>> <otavio at ossystems.com.br> wrote:
>>> On Thu, Feb 28, 2013 at 7:50 AM, Zhenhua Luo <zhenhua.luo at freescale.com> wrote:
>>>> conf/distro/fsl.conf has been removed, meta-fsl-ppc is not distro specific.
>>>> Signed-off-by: Zhenhua Luo <zhenhua.luo at freescale.com>
>>> I do support this move (as indeed the BSP shouldn't be distro
>>> specific) however this change breaks upgrade path from existend users.
>>> Please use:
>>> PRINC := "${@int(PRINC) + 1}"
>> I don't think this works properly for bbapends. When the base recipes
>> bumps the PR the there will be overlapping PRs which will cause
>> conflicts... or maybe I am missing something.
> In fact it does work. When the base recipe change PR, let's say r1 to
> r2, for each PRINC it will be raised. So in this case it will be r3.
>> I think the common practice is to not do anything to the PR for
>> bbappends. Even though we used to do this ${DISTRO} append.
> For PR, yes. But for PRINC you should.
> (adding Richard in Cc)
> Richard, the PRServer will handle the removal of PR suffix in this
> case? What it'd do?

Sorry, I was confusing myself here... this looks to in fact be the
common practice.


More information about the meta-freescale mailing list