* SRC_URI and latest HEAD revision with git @ 2013-07-22 6:21 Steffen Sledz 2013-07-22 9:01 ` Nicolas Dechesne 0 siblings, 1 reply; 21+ messages in thread From: Steffen Sledz @ 2013-07-22 6:21 UTC (permalink / raw) To: openembedded-core 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. 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 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 0 siblings, 1 reply; 21+ messages in thread From: Nicolas Dechesne @ 2013-07-22 9:01 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-core [-- Attachment #1: Type: text/plain, Size: 646 bytes --] On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <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/distro/include/poky-floating-revisions.inc [-- Attachment #2: Type: text/html, Size: 1282 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-22 9:01 ` Nicolas Dechesne @ 2013-07-22 9:46 ` Steffen Sledz 2013-07-22 9:51 ` Paul Eggleton 0 siblings, 1 reply; 21+ messages in thread From: Steffen Sledz @ 2013-07-22 9:46 UTC (permalink / raw) To: Nicolas Dechesne; +Cc: openembedded-core 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/distro/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. Regards, 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-22 9:46 ` Steffen Sledz @ 2013-07-22 9:51 ` Paul Eggleton 2013-07-22 10:30 ` Steffen Sledz 2013-07-31 10:02 ` [OE-core] " Steffen Sledz 0 siblings, 2 replies; 21+ messages in thread From: Paul Eggleton @ 2013-07-22 9:51 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-core 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/distr > > 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 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-22 9:51 ` Paul Eggleton @ 2013-07-22 10:30 ` Steffen Sledz 2013-07-22 11:08 ` Paul Eggleton 2013-07-31 10:02 ` [OE-core] " Steffen Sledz 1 sibling, 1 reply; 21+ messages in thread From: Steffen Sledz @ 2013-07-22 10:30 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-core 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/distr >>> 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? * What modifications in bitbake.conf, local.conf, ... are necessary? Regards, 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 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 0 siblings, 2 replies; 21+ messages in thread From: Paul Eggleton @ 2013-07-22 11:08 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-core 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. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-22 11:08 ` Paul Eggleton @ 2013-07-22 12:42 ` Martin Jansa 2013-07-23 6:23 ` Steffen Sledz 1 sibling, 0 replies; 21+ messages in thread From: Martin Jansa @ 2013-07-22 12:42 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-core [-- Attachment #1: Type: text/plain, Size: 2755 bytes --] On Mon, Jul 22, 2013 at 12:08:06PM +0100, 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. If you need to support upgrade path from old LOCALCOUNT db in PERSISTENT_DIR then you also need to migrate last numbers to PRSERV db. -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-22 11:08 ` Paul Eggleton 2013-07-22 12:42 ` Martin Jansa @ 2013-07-23 6:23 ` Steffen Sledz 2013-07-23 8:20 ` Paul Eggleton 1 sibling, 1 reply; 21+ messages in thread From: Steffen Sledz @ 2013-07-23 6:23 UTC (permalink / raw) To: Paul Eggleton, openembedded-core 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git 2013-07-23 6:23 ` Steffen Sledz @ 2013-07-23 8:20 ` Paul Eggleton 0 siblings, 0 replies; 21+ messages in thread From: Paul Eggleton @ 2013-07-23 8:20 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-core On Tuesday 23 July 2013 08:23:54 Steffen Sledz wrote: > 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: > >>> 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? Perhaps confusingly it's part of OE-Core. I haven't looked at it to see if there's anything OE-specific about it that meant it had to be there rather than supplied with bitbake. > * Does anyone have systemd configs or sysvinit scripts for handling the > bitbake-prserv? I don't, but perhaps others do. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: SRC_URI and latest HEAD revision with git (in oe-classic) 2013-07-22 9:51 ` Paul Eggleton @ 2013-07-31 10:02 ` Steffen Sledz 2013-07-31 10:02 ` [OE-core] " Steffen Sledz 1 sibling, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-07-31 10:02 UTC (permalink / raw) To: openembedded-core, openembedded-devel; +Cc: Paul Eggleton 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/distr >>> 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? 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-07-31 10:02 ` Steffen Sledz 0 siblings, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-07-31 10:02 UTC (permalink / raw) To: openembedded-core, openembedded-devel; +Cc: Paul Eggleton 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/distr >>> 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? 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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic) 2013-07-31 10:02 ` [OE-core] " Steffen Sledz @ 2013-07-31 12:50 ` Paul Eggleton -1 siblings, 0 replies; 21+ messages in thread From: Paul Eggleton @ 2013-07-31 12:50 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-devel, openembedded-core 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@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 > > 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. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-07-31 12:50 ` Paul Eggleton 0 siblings, 0 replies; 21+ messages in thread From: Paul Eggleton @ 2013-07-31 12:50 UTC (permalink / raw) To: Steffen Sledz; +Cc: openembedded-devel, openembedded-core 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@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 > > 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. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic) 2013-07-31 12:50 ` [OE-core] " Paul Eggleton @ 2013-08-01 6:11 ` Steffen Sledz -1 siblings, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-08-01 6:11 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-devel, openembedded-core 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@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 >> >> 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@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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-08-01 6:11 ` Steffen Sledz 0 siblings, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-08-01 6:11 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-devel, openembedded-core 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@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 >> >> 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@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 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic) 2013-08-01 6:11 ` [OE-core] " Steffen Sledz @ 2013-08-01 10:36 ` Martin Jansa -1 siblings, 0 replies; 21+ messages in thread From: Martin Jansa @ 2013-08-01 10:36 UTC (permalink / raw) To: openembedded-devel; +Cc: Paul Eggleton, openembedded-core [-- Attachment #1: Type: text/plain, Size: 4257 bytes --] On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: > 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@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 > >> > >> 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? BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). > 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 > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-08-01 10:36 ` Martin Jansa 0 siblings, 0 replies; 21+ messages in thread From: Martin Jansa @ 2013-08-01 10:36 UTC (permalink / raw) To: openembedded-devel; +Cc: Paul Eggleton, openembedded-core [-- Attachment #1: Type: text/plain, Size: 4257 bytes --] On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: > 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@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 > >> > >> 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? BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). > 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 > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic) 2013-08-01 10:36 ` [OE-core] " Martin Jansa @ 2013-08-01 10:52 ` Steffen Sledz -1 siblings, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-08-01 10:52 UTC (permalink / raw) To: openembedded-devel; +Cc: Paul Eggleton, openembedded-core -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.08.2013 12:36, Martin Jansa wrote: > On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: >> On 31.07.2013 14:50, Paul Eggleton wrote: >>> On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote: >> ... 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? > > BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). Every git repo? Or every git repo used with AUTOREV only? > empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). That should be OK for us. - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa bagAnidiDoZO6PtViGA9zJfSRa+n4IcK =rQan -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-08-01 10:52 ` Steffen Sledz 0 siblings, 0 replies; 21+ messages in thread From: Steffen Sledz @ 2013-08-01 10:52 UTC (permalink / raw) To: openembedded-devel; +Cc: Paul Eggleton, openembedded-core -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.08.2013 12:36, Martin Jansa wrote: > On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: >> On 31.07.2013 14:50, Paul Eggleton wrote: >>> On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote: >> ... 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? > > BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). Every git repo? Or every git repo used with AUTOREV only? > empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). That should be OK for us. - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa bagAnidiDoZO6PtViGA9zJfSRa+n4IcK =rQan -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic) 2013-08-01 10:52 ` [OE-core] " Steffen Sledz @ 2013-08-01 11:37 ` Martin Jansa -1 siblings, 0 replies; 21+ messages in thread From: Martin Jansa @ 2013-08-01 11:37 UTC (permalink / raw) To: Steffen Sledz; +Cc: Paul Eggleton, openembedded-devel, openembedded-core [-- Attachment #1: Type: text/plain, Size: 1820 bytes --] On Thu, Aug 01, 2013 at 12:52:53PM +0200, Steffen Sledz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01.08.2013 12:36, Martin Jansa wrote: > > On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: > >> On 31.07.2013 14:50, Paul Eggleton wrote: > >>> On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote: > >> ... 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? > > > > BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). > > Every git repo? Or every git repo used with AUTOREV only? Every git repo with SRCPV. > > empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). > > That should be OK for us. > > - -- > 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa > bagAnidiDoZO6PtViGA9zJfSRa+n4IcK > =rQan > -----END PGP SIGNATURE----- -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic) @ 2013-08-01 11:37 ` Martin Jansa 0 siblings, 0 replies; 21+ messages in thread From: Martin Jansa @ 2013-08-01 11:37 UTC (permalink / raw) To: Steffen Sledz; +Cc: Paul Eggleton, openembedded-devel, openembedded-core [-- Attachment #1: Type: text/plain, Size: 1820 bytes --] On Thu, Aug 01, 2013 at 12:52:53PM +0200, Steffen Sledz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01.08.2013 12:36, Martin Jansa wrote: > > On Thu, Aug 01, 2013 at 08:11:48AM +0200, Steffen Sledz wrote: > >> On 31.07.2013 14:50, Paul Eggleton wrote: > >>> On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote: > >> ... 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? > > > > BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone). > > Every git repo? Or every git repo used with AUTOREV only? Every git repo with SRCPV. > > empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed). > > That should be OK for us. > > - -- > 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa > bagAnidiDoZO6PtViGA9zJfSRa+n4IcK > =rQan > -----END PGP SIGNATURE----- -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2013-08-01 11:37 UTC | newest] Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 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
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.