All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: SRC_URI and latest HEAD revision with git
Date: Tue, 23 Jul 2013 08:23:54 +0200	[thread overview]
Message-ID: <51EE217A.4040709@dresearch-fe.de> (raw)
In-Reply-To: <3148065.skdr24gULv@helios>

On 22.07.2013 13:08, Paul Eggleton wrote:
> On Monday 22 July 2013 12:30:53 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@dresearch-fe.de
>>>>>
>>>>> <mailto:sledz@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
>>
>> This seems to be the thing we need.
>>
>> But the description is not very helpful from the view of a recipe
>> maintainer. It describes mostly the server part.
>>
>> * What do i have to write in my recipe?
> 
> Nothing special. If you used SRCPV in PV where you are using an SCM in 
> SRC_URI, that should be enough. The integer at the start of SRCREV will be 
> incremented automatically if the revision changes, and if it doesn't but other 
> values within the recipe change then PR will automatically be incremented 
> above the initial value set in the recipe.
> 
>> * What modifications in bitbake.conf, local.conf, ... are necessary?
> 
> I believe as described in the page I linked above you should only need to set 
> PRSERV_HOST.

You're right. This works. ;-)

I've two points more:
* The Wiki-Page mentions the bitbake-prserv-tool. Where can this be found? It does not seem to be part of the bitbake repo.
* Does anyone have systemd configs or sysvinit scripts for handling the bitbake-prserv?

Cheers,
Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@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


  parent reply	other threads:[~2013-07-23  6:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  6:21 SRC_URI and latest HEAD revision with git Steffen Sledz
2013-07-22  9:01 ` Nicolas Dechesne
2013-07-22  9:46   ` Steffen Sledz
2013-07-22  9:51     ` Paul Eggleton
2013-07-22 10:30       ` Steffen Sledz
2013-07-22 11:08         ` Paul Eggleton
2013-07-22 12:42           ` Martin Jansa
2013-07-23  6:23           ` Steffen Sledz [this message]
2013-07-23  8:20             ` Paul Eggleton
2013-07-31 10:02       ` SRC_URI and latest HEAD revision with git (in oe-classic) Steffen Sledz
2013-07-31 10:02         ` [OE-core] " Steffen Sledz
2013-07-31 12:50         ` [oe] " Paul Eggleton
2013-07-31 12:50           ` [OE-core] " Paul Eggleton
2013-08-01  6:11           ` [oe] " Steffen Sledz
2013-08-01  6:11             ` [OE-core] " Steffen Sledz
2013-08-01 10:36             ` [oe] " Martin Jansa
2013-08-01 10:36               ` [OE-core] " Martin Jansa
2013-08-01 10:52               ` [oe] " Steffen Sledz
2013-08-01 10:52                 ` [OE-core] " Steffen Sledz
2013-08-01 11:37                 ` [oe] " Martin Jansa
2013-08-01 11:37                   ` [OE-core] " Martin Jansa

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=51EE217A.4040709@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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.