unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: prefetch tarballs in a batch
Date: Sun, 13 Apr 2014 00:44:02 +0200	[thread overview]
Message-ID: <87bnw6yxql.fsf@gnu.org> (raw)
In-Reply-To: <87ioqe2tdg.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sun, 13 Apr 2014 00:19:23 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>>> 1. Should the recursion stop when ‘fixed-output-derivation?’ returns #t?
>
>> I think so.  In general fixed-output derivations are the things you
>> would like to pre-fetch; so you would typically call ‘build-derivations’
>> on these to do the actual pre-fetching.
>
> Could you show a package with a fixed-output derivation?  My current
> implementation calls itself indefinitely because the base case is never
> satisfied.

Any “origin” that has no patches/snippet is a fixed-output derivation.

But!  There was a bug in ‘fixed-output-derivation?’ (which was actually
unused until now.)  Fixed in 99e17dc:

--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (package-source-derivation s (package-source wget))
$12 = #<derivation /gnu/store/f96502xhla1k3daikjckn2zb1l17m8r5-wget-1.15.tar.xz.drv => /gnu/store/qz9vm8802v6pi69ci2kgnvfivrkr085r-wget-1.15.tar.xz 2d1e730>
scheme@(guile-user)> (fixed-output-derivation? $12)
$13 = #t
--8<---------------cut here---------------end--------------->8---

Thanks!

Ludo’.

  reply	other threads:[~2014-04-12 22:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 23:25 Proposal: prefetch tarballs in a batch Nikita Karetnikov
2014-03-28 13:23 ` Ludovic Courtès
2014-04-01 23:23   ` Nikita Karetnikov
2014-04-02 12:57     ` Ludovic Courtès
2014-04-02 22:37       ` Nikita Karetnikov
2014-04-03  7:24         ` Ludovic Courtès
2014-04-09 22:29           ` Nikita Karetnikov
2014-04-10  8:21             ` Ludovic Courtès
2014-04-12 20:19               ` Nikita Karetnikov
2014-04-12 22:44                 ` Ludovic Courtès [this message]
2014-04-24 21:20                   ` Nikita Karetnikov
2014-04-25 11:51                     ` Ludovic Courtès
2014-04-25 12:04                     ` Ludovic Courtès
2014-05-06 12:37                       ` Nikita Karetnikov
2014-05-06 20:02                         ` Ludovic Courtès
2014-05-07 23:14                           ` Nikita Karetnikov
2014-05-08 16:35                             ` Ludovic Courtès
2014-05-11 14:52                               ` Nikita Karetnikov
2014-05-11 19:17                                 ` Ludovic Courtès
2014-09-02 21:06                                   ` Ludovic Courtès
2014-09-02 22:05                                     ` Nikita Karetnikov
2014-09-02 21:04                               ` Ludovic Courtès

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=87bnw6yxql.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=nikita@karetnikov.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).