From: David Craven <david@craven.ch>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 07/24] gnu: compression: Add snappy.
Date: Thu, 18 Aug 2016 14:41:44 +0200 [thread overview]
Message-ID: <CAL1_imkJfkEmAuYoaa3neG4T3acc1gfQQzC-ZXfxSVa62jFi3g@mail.gmail.com> (raw)
In-Reply-To: <87pop6pmnl.fsf@gmail.com>
> I wonder, are there any drawbacks of making the linter check that the
> URL provides the data named by the hash?
That may be useful. I think if guix refresh would accept a version
flag, and possibly a force flag, that would also be useful.
The version flag would be used as follows:
guix refresh qtbase -u --version=5.7.0
If the version is already set to 5.7.0 a -f flag would download and
update the hash anyway. This is useful when the download url has
changed, but the version hasn't as in the snappy example. I think
these two features could make guix refresh more generally applicable,
to packages that don't have an automatic updater.
next prev parent reply other threads:[~2016-08-18 12:41 UTC|newest]
Thread overview: 11+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 18:39 [PATCH 01/24] gnu: qt: Add qtquickcontrols David Craven
2016-08-16 18:39 ` [PATCH 07/24] gnu: compression: Add snappy David Craven
2016-08-16 19:45 ` Alex Kost
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=CAL1_imkJfkEmAuYoaa3neG4T3acc1gfQQzC-ZXfxSVa62jFi3g@mail.gmail.com \
--to=david@craven.ch \
--cc=alezost@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.