All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)
Date: Thu, 1 Aug 2013 13:37:36 +0200	[thread overview]
Message-ID: <20130801113736.GO3280@jama> (raw)
In-Reply-To: <51FA3E05.2070205@dresearch-fe.de>

[-- 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 --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] SRC_URI and latest HEAD revision with git (in oe-classic)
Date: Thu, 1 Aug 2013 13:37:36 +0200	[thread overview]
Message-ID: <20130801113736.GO3280@jama> (raw)
In-Reply-To: <51FA3E05.2070205@dresearch-fe.de>

[-- 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 --]

  reply	other threads:[~2013-08-01 11:37 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
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                 ` Martin Jansa [this message]
2013-08-01 11:37                   ` 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=20130801113736.GO3280@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=sledz@dresearch-fe.de \
    /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.