From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: Default SRCREV value
Date: Wed, 19 Mar 2008 22:04:37 -0400 [thread overview]
Message-ID: <47E1C635.3030702@balister.org> (raw)
In-Reply-To: <200803200120.47119.zecke@selfish.org>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hmm, I am asleep at the wheel today. Good suggeestion!
Philip
Holger Freyther wrote:
> 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.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-03-20 2:04 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
2008-03-20 2:04 ` Philip Balister [this message]
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=47E1C635.3030702@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.