From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: commit 9b9a2409c7e2ddb2caf0a5aba74549f65c52b503
Date: Tue, 26 Feb 2008 08:19:04 -0500 [thread overview]
Message-ID: <47C411C8.5030204@balister.org> (raw)
In-Reply-To: <47C3D204.9090908@dominion.kabel.utwente.nl>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> - --- packages/netsurf/netsurf_svn.bb
> c00865f4500c29a5271184c5babd7fc2a83ef465
> +++ packages/netsurf/netsurf_svn.bb c00865f4500c29a5271184c5babd7fc2a83ef465
> @@ -0,0 +1,43 @@
>
> +PV = "1.1+svn${SRCDATE}"
>
> That's bogus, svn repos must use SRCREV with an entry in
> sane-srcrevs.inc in OE.
Basically this should be:
+PV = "1.1+svnr${SRCREV}"
and the sane-srcrevs files should add an entry for a rev that will build.
When I build svn based stuff and want to use the latest rev, I put
something like:
SRCREV_pn-linux-davinci ?= ${AUTOREV}
in local.conf. Do not put AUTOREV in the sane-srcrev file. The AUTOREV
forces bitbake to check the current version in the repo and this gets
really slow.
And yes, I really should write a FAQ entry on this ....
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-02-26 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 8:47 commit 9b9a2409c7e2ddb2caf0a5aba74549f65c52b503 Koen Kooi
2008-02-26 13:19 ` Philip Balister [this message]
2008-02-26 14:52 ` Rolf Leggewie
2008-02-28 5:52 ` Junqian Gordon Xu
2008-02-28 10:12 ` Rolf Leggewie
2008-02-28 6:05 ` Junqian Gordon Xu
2008-02-28 6:08 ` Junqian Gordon Xu
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=47C411C8.5030204@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.