From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Improving SRCPV? (was: Re: [PATCH 3/7] gptfdisk: update to 1.0.0)
Date: Mon, 10 Aug 2015 15:29:48 +0300 [thread overview]
Message-ID: <55C8993C.2070303@linux.intel.com> (raw)
In-Reply-To: <1439162974.30467.156.camel@linuxfoundation.org>
On 08/10/2015 02:29 AM, Richard Purdie wrote:
>> its always preferable to have PV contain SRCPV for recipes using SCM based fetch mechanism. Don’t drop it
>
> There has been discussion about this in other threads and the conclusion
> reached is that where there is a specific version being selected, having
> PV of that specific version is a good thing. With "1.0.0+gitXXX" its
> unclear if its really 1.0.0 or not.
Yes. When SCM is used to fetch a pristine tagged release, adding SRCPV
just adds unnecessary clutter. My understanding is that SRCPV is only
there to enforce package version going forwards when changing one git
snapshot for a later git snapshot, when both are based on the same
tagged release.
Alex
next prev parent reply other threads:[~2015-08-10 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 14:28 [PATCH 0/7] More recipe reporting fixes Alexander Kanavin
2015-08-07 14:28 ` [PATCH 1/7] fotowall: update SRC_URI to use github instead of qt-apps.org Alexander Kanavin
2015-08-07 14:28 ` [PATCH 2/7] distcc: update SRC_URI to not use Google Code Alexander Kanavin
2015-08-08 19:49 ` Khem Raj
2015-08-07 14:28 ` [PATCH 3/7] gptfdisk: update to 1.0.0 Alexander Kanavin
2015-08-08 19:48 ` Khem Raj
2015-08-09 23:29 ` Richard Purdie
2015-08-10 12:29 ` Alexander Kanavin [this message]
2015-08-07 14:28 ` [PATCH 4/7] oprofile: reorder SRC_URI lines to fix upstream version check Alexander Kanavin
2015-08-07 14:28 ` [PATCH 5/7] xf86-video-omapfb: switch SRC_URI to debian git repo Alexander Kanavin
2015-08-07 14:28 ` [PATCH 6/7] stress: update checksums to match upstream tarball, use BPN and BP in SRC_URI Alexander Kanavin
2015-08-07 14:28 ` [PATCH 7/7] recipeutils.py: allow all characters in regexes used to parse version strings Alexander Kanavin
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=55C8993C.2070303@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox