From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix-shell?
Date: Mon, 22 Sep 2014 09:40:36 +0200 [thread overview]
Message-ID: <87y4tct85n.fsf@gnu.org> (raw)
In-Reply-To: <87y4tcvjer.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 21 Sep 2014 21:54:36 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> What about:
>
> 1. Computing the list of search-path-specifications of all the
> transitive inputs of the package, the way ‘package-derivation’
> does it;
>
> 2. Computing, based on these specifications and all the input
> derivations, the actual search paths, the way ‘set-paths’ does it?
As discussed on IRC, that won’t work because ‘build-system’
implementations augment the search path specifications on their own, and
there’s no good way from the outside to tell what these are.
Bummer.
Ludo’.
prev parent reply other threads:[~2014-09-22 7:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 9:22 Back from GHM Ludovic Courtès
2014-08-25 11:57 ` Amirouche Boubekki
2014-08-25 13:47 ` Thompson, David
2014-08-25 15:38 ` Amirouche Boubekki
2014-08-25 22:24 ` guix-shell? Ludovic Courtès
2014-08-26 11:32 ` guix-shell? David Thompson
2014-08-28 15:45 ` guix-shell? Ludovic Courtès
2014-08-26 12:14 ` guix-shell? David Thompson
2014-08-26 20:20 ` guix-shell? Andreas Enge
2014-08-26 20:31 ` guix-shell? David Thompson
2014-08-28 12:39 ` guix-shell? Amirouche Boubekki
2014-08-28 15:50 ` guix-shell? Ludovic Courtès
2014-08-30 2:03 ` guix-shell? David Thompson
2014-08-31 15:00 ` guix-shell? Ludovic Courtès
2014-09-18 2:22 ` guix-shell? David Thompson
2014-09-18 8:00 ` guix-shell? Ludovic Courtès
2014-09-21 17:25 ` guix-shell? David Thompson
2014-09-21 19:54 ` guix-shell? Ludovic Courtès
2014-09-22 7:40 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4tct85n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--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.