From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: SCM fetched recipes without a SRCREV - e.g. libgee-native
Date: Wed, 21 Oct 2009 12:47:41 +0200 [thread overview]
Message-ID: <hbmose$gtv$1@ger.gmane.org> (raw)
Hi,
Lately some people have started adding recipes that fetch from an SCM
without adding a srcrev either to the recipe or to sane-srcrevs.inc.
That is bad. Unacceptable even.
e.g.
http://dominion.thruhere.net/git/cgit.cgi/openembedded/commit/?id=cd473395ebf9adbf04ff4235878615cfa25daaf7
Previously it only affected recipes I don't care about, but the
libgee-native one breaks my build. I seem to recall we declared taboo on
recipes that have a floating srcrev by default, but I guess people think
that "no srcrev at all" doesn't fit that category. It does.
So please add a srcrev or revert the cset.
Koen
next reply other threads:[~2009-10-21 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 10:47 Koen Kooi [this message]
2009-10-21 11:03 ` SCM fetched recipes without a SRCREV - e.g. libgee-native Holger Hans Peter Freyther
2009-10-21 11:10 ` Michael 'Mickey' Lauer
2009-10-21 11:21 ` Koen Kooi
2009-10-21 11:42 ` Michael 'Mickey' Lauer
2009-10-21 18:57 ` Richard Purdie
2009-10-22 0:59 ` Denys Dmytriyenko
2009-10-22 8:44 ` Richard Purdie
2009-10-21 11:15 ` Robert P. J. Day
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='hbmose$gtv$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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