From: Nikita Karetnikov <nikita@karetnikov.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: prefetch tarballs in a batch
Date: Wed, 02 Apr 2014 03:23:53 +0400 [thread overview]
Message-ID: <87wqf8prau.fsf@karetnikov.org> (raw)
In-Reply-To: <877g7epico.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 28 Mar 2014 14:23:35 +0100")
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
> The simplest way to do it would be by walking the package DAG: start
> from ‘foo’, accumulate its ‘package-source’, then traverse its inputs,
> etc. Recursion would stop at the implicit inputs (GCC, glibc,
> Coreutils, etc.), though.
> If you’d like implicit inputs to be taken into account, then you’d have
> to traverse derivations. It’s less convenient because it’s lower-level.
Is there a function that accepts a package name and returns a list of
implicit inputs?
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2014-04-01 23:29 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 [this message]
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
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=87wqf8prau.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--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).