[OE-core] [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

[Steffen Sledz]

On 31.07.2013 14:50, Paul Eggleton wrote:
> On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:
>> On 22.07.2013 11:51, Paul Eggleton wrote:
>>> On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
>>>> On 22.07.2013 11:01, Nicolas Dechesne wrote:
>>>>> On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <sledz at dresearch-fe.de
>>>>>
>>>>> <mailto:sledz at dresearch-fe.de>> wrote:
>>>>>> After being OE abstinent for some months i'd like to ask what is the
>>>>>> current suggested method for recipes building from the HEAD revision of
>>>>>> a git repository (we need this for continuous integration).
>>>>>>
>>>>>> I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final
>>>>>> decision, documentation and a good example.>
>>>>>
>>>>> you can use ${AUTOREV} for this purpose. You can look at poky-bleeding
>>>>> distro config for such an example.
>>>>>
>>>>> e.g.
>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
>>>>> r
>>>>> o/include/poky-floating-revisions.inc
>>>>
>>>> Hmmmm? This doesn't seem the work.
>>>>
>>>> Here's what i tried in my recipe:
>>>>
>>>> ------------> snip <------------
>>>> PR = "r3"
>>>>
>>>> SRCREV="${AUTOREV}"
>>>> PV = "gitr${SRCPV}"
>>>> ------------> snip <------------
>>>>
>>>> But i get package versions like
>>>>
>>>>   gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
>>>>
>>>> where SRCPB is always 0. :(
>>>>
>>>> A bit more description and/or a complete example would be very helpful.
>>>
>>> If you want these to increment now AIUI you need to be using the PR
>>> server:
>>>
>>> https://wiki.yoctoproject.org/wiki/PR_Service
>>
>> And here comes my next really big problem. :(
>>
>> We're sitting on an big, old but active project based on oe-classic and
>> bitbake 1.12.0. Irksomely we're forced to switch from SVN to GIT for this
>> project. So we need the AUTOREV/PRSERV stuff for this old environment too.
>>
>> Has anyone tried to backport the feature to an older bitbake/oe-classic
>> environment? Or can someone give some hints what's to do?
> 
> I'm not sure, but my gut feeling is you'd be better off trying to bring the 
> project up to be based on OE-Core rather than trying to bring such 
> functionality back to OE-Classic, particularly since for full functionality it 
> requires signature-based tasks that are only supported with current versions 
> of bitbake and require support from the metadata. You'd be trading some 
> hopefully short-term pain for long-term gain if the project is going to 
> continue for a reasonable amount of time.

I was afraid to get this answer. ;-)

Unfortunately we do not have the manpower to bring up this old project to oe-core. Our team is working hard on a follow-up project based on oe-core.

I read something about a solution using

  BB_GIT_CLONE_FOR_SRCREV = "1"
  BB_LOCALCOUNT_OVERRIDE = ""

which should be supported by the old oe-classic/bitbake-1.12.0. Could this be a solution for our problem? What drawbacks does it have?

Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz at dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058