Re: [PATCH 00/11] Add read PV into recipes

[Paul Eggleton <paul.eggleton@linux.intel.com>]

Hi Emilia,

On Thursday 18 July 2013 17:16:24 Emilia Ciobanu wrote:
> Tested for backwards packages.
> 
> The following changes since commit 3dee534f1e25109e0bdb681de0746c336f4b8840:
> 
>   lib/oeqa: fix dependecy check (2013-07-16 10:04:17 +0100)
> 
> are available in the git repository at:
> 
>   git://git.yoctoproject.org/poky-contrib emac/pv_fixes
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=emac/pv_fixes
> 
> Emilia Ciobanu (11):
>   rt-tests: add PV variable into recipe
>   kmod: add PV variable into recipe
>   hwlatdetect: add PV variable into recipe
>   lttng-ust: add PV variable into recipe
>   connman-gnome: add PV variable into recipe
>   mtd-utils: add PV variable into recipe
>   update-rc.d: add PV variable into recipe
>   build-appliance-image: add PV variable into recipe
>   lttng-modules: Append _git to recipe name and update PV with git
>     token
>   chkconfig-alternatives-native: add git token in package version
>   docbook-sgml-dtd-4.5-native.bb: Add real PV inside the recipe

Reviewing these for the consolidated pull I noticed that one or two change the 
filename to _git (or that's already the filename) whereas others don't. 

For recipes that do point to a git repository but are fetching the revision 
tagged for a release, it is correct to say they have a fixed PV without 
+git${SRCPV}, which is why we have done this. However, perhaps for consistency 
and avoidance of future confusion if SRCREV is changed we should ignore this.

When the recipe does set PV, it is probably best that the recipe's filename 
doesn't contain a specific version otherwise it could be that it gets upgraded 
later and the version in the filename no longer matches the new PV value. 
Therefore I'd suggest If PV is being set and the recipe is fetching from a git 
repository, we should rename the recipe to use _git.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre