From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: ‘guix lint’ URL checks
Date: Tue, 30 Aug 2016 14:28:03 -0400 [thread overview]
Message-ID: <20160830182803.GD2595@jasmine> (raw)
In-Reply-To: <8737lp6c3a.fsf_-_@gnu.org>
On Sun, Aug 28, 2016 at 01:12:09AM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> > I wonder, are there any drawbacks of making the linter check that the
> > URL provides the data named by the hash?
>
> The rationale so far was that ‘guix lint foo’ should be fast (a couple
> of seconds at most), and ‘guix lint’ (all packages) should complete in
> less than a day. ;-)
Reasonable :)
> Thus, the ‘source’ and ‘home-page’ checks simply ensure that the URI
> points to something accessible instead of actually downloading the
> thing. This is fast and catches the most obvious errors, but has the
> drawback of not catching the right-URL-wrong-hash kind of errors.
I guess that `guix build --check --source foo` is the right way to check
for this mistake.
prev parent reply other threads:[~2016-08-30 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 8:30 [PATCH 07/24] gnu: compression: Add snappy David Craven
2016-08-17 19:02 ` Alex Kost
2016-08-17 19:20 ` David Craven
2016-08-17 19:27 ` David Craven
2016-08-18 7:21 ` Alex Kost
2016-08-18 12:41 ` David Craven
2016-08-18 1:25 ` Leo Famulari
2016-08-27 23:12 ` ‘guix lint’ URL checks Ludovic Courtès
2016-08-30 18:28 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160830182803.GD2595@jasmine \
--to=leo@famulari.name \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).