All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: About PV = "0.0+git${SRCPV}"
Date: Fri, 22 Apr 2016 09:40:12 +0800	[thread overview]
Message-ID: <571980FC.3020100@windriver.com> (raw)
In-Reply-To: <1461224521.31320.112.camel@linuxfoundation.org>



On 04/21/2016 03:42 PM, Richard Purdie wrote:
> On Thu, 2016-04-21 at 15:22 +0800, Robert Yang wrote:
>> There are several recipes in oe-core which has:
>> PV = "0.0+git${SRCPV}"
>>
>> These recipes don't have a release version, so we use
>> "0.0+git${SRCPV}",
>> but the package manager such as opkg/rpm/smart may not upgrade them
>> correctly when the recipes is upgraded since we can't make sure that
>> SRCPV_new > SRCPV_old.
>>
>> How about we use date for these recipes which doesn't have a release
>> version? For example, if we integrate them to oe-core today, then
>> PV = "20160421". And when we upgrade them in the future, we can
>> change
>> the PV to that day. We can change all the current version 0.0 target
>> recipes to today, and add a sanity check for version 0.0.
>
> No, this is the whole idea behind having the PR Server which injects a
> revision before the hash in SRCPV. We have the same problem with other
> git recipes even where there are versions since the revision can change
> and we need to be able to sort the versions correctly.

Thanks, I saw that PR Server will change git0 -> git1 -> git2 when SRCREV
is changed, it works.

// Robert

>
> Cheers,
>
> Richard
>


      reply	other threads:[~2016-04-22  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  7:22 About PV = "0.0+git${SRCPV}" Robert Yang
2016-04-21  7:42 ` Richard Purdie
2016-04-22  1:40   ` Robert Yang [this message]

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=571980FC.3020100@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.