All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: Default SRCREV value
Date: Wed, 19 Mar 2008 19:50:35 -0400	[thread overview]
Message-ID: <47E1A6CB.4010708@balister.org> (raw)
In-Reply-To: <878x0emgub.fsf@frontier.dottedmag.net>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Mikhail Gusarov wrote:
> Hello,
> 
> I've stumbled upon SRCREV="1" setting if bitbake.conf today, debugging
> misterious mis-build of pkg-native.
> 
> Shouldn't SRCREV default to ${AUTOREV} or something like
> ${sys.write("Please define SRCREV"}; sys.exit(1)} ? Default value of "1"
> is hardly useful.

We know :)

But defaulting to ${AUTOREV} causes builds to fail if the repository is 
offline during parsing and checking AUTOREV during parsing is a slow 
process.

Setting SRCREV to 1 is not a good solution, but it is better than all 
the alternatives. Personally, I wish bitbake would print a HUGE message 
when it tries to fetch a SRCREV of 1 telling people to update a 
preferred version file or add AUTOREV to a local conf file. (I have 
AUTOREV in my local.conf for a few bb files where I mean AUTOREV)

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2008-03-19 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 23:31 Default SRCREV value Mikhail Gusarov
2008-03-19 23:50 ` Philip Balister [this message]
2008-03-20  0:20   ` Holger Freyther
2008-03-20  2:04     ` Philip Balister
2008-03-20  8:06     ` Mikhail Gusarov
2008-03-20  9:46     ` Leon Woestenberg

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=47E1A6CB.4010708@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.