From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: RFC: Making it mandantory to have a checksums.ini entry
Date: Wed, 1 Oct 2008 04:47:41 +0200 [thread overview]
Message-ID: <200810010447.44667.zecke@selfish.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
Hey,
I constantly spend my day moving checksums from tmp/checksums.ini to the right
place and I would like to make it mandatory to have a checksums.ini entry
when adding new versions.
The spend time on copy and pasting a checksums.ini entry is really small and
the value is very high. Stuff like macports is forcing one to have checksums
as well.
The attached diff would force it.
comments appreciated
z.
[-- Attachment #2: make-it-mandantory.diff --]
[-- Type: text/x-diff, Size: 801 bytes --]
diff --git a/classes/base.bbclass b/classes/base.bbclass
index 2025483..a2a93c8 100644
--- a/classes/base.bbclass
+++ b/classes/base.bbclass
@@ -602,7 +602,10 @@ python base_do_fetch() {
try:
if type == "http" or type == "https" or type == "ftp" or type == "ftps":
if not base_chk_file(parser, pn, pv,uri, localpath, d):
- bb.note("%s-%s: %s has no entry in conf/checksums.ini, not checking URI" % (pn,pv,uri))
+ if not bb.data.getVar("OE_ALLOW_INSECURE_DOWNLOADS",d, True):
+ bb.fatal("%s-%s: %s has no entry in conf/checksums.ini, not checking URI" % (pn,pv,uri))
+ else:
+ bb.note("%s-%s: %s has no entry in conf/checksums.ini, not checking URI" % (pn,pv,uri))
except Exception:
raise bb.build.FuncFailed("Checksum of '%s' failed" % uri)
}
next reply other threads:[~2008-10-01 2:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:47 Holger Freyther [this message]
2008-10-01 2:58 ` RFC: Making it mandantory to have a checksums.ini entry Otavio Salvador
2008-10-01 7:06 ` Koen Kooi
2008-10-15 17:34 ` Holger Freyther
2008-10-15 17:51 ` Koen Kooi
2008-10-15 18:17 ` Marcin Juszkiewicz
2008-10-16 12:20 ` Sledz, Steffen
2008-10-16 12:39 ` Thomas Kunze
2008-10-16 12:44 ` Sledz, Steffen
2008-10-16 12:52 ` Thomas Kunze
2008-10-16 13:12 ` Sledz, Steffen
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=200810010447.44667.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 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.