Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Default SRCREV value
Date: Thu, 20 Mar 2008 01:20:47 +0100	[thread overview]
Message-ID: <200803200120.47119.zecke@selfish.org> (raw)
In-Reply-To: <47E1A6CB.4010708@balister.org>

On Thursday 20 March 2008 00:50:35 Philip Balister wrote:

> 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.

Or as Mikhail suggested:
${@bb.fatal("You want to specify a sane srvrev")}

The only down-side I can think of, now parsing will fail for a recipe you do 
not even care for in your distribution, with having a default value 1 you 
just parse fine.


z.



  reply	other threads:[~2008-03-20  0:21 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
2008-03-20  0:20   ` Holger Freyther [this message]
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=200803200120.47119.zecke@selfish.org \
    --to=zecke@selfish.org \
    --cc=openembedded-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox