unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19816-done@debbugs.gnu.org, Dave Thompson <davet@gnu.org>
Subject: bug#19816: 'guix environment' always downloads all the outputs of dependencies
Date: Fri, 12 Feb 2016 16:37:38 -0500	[thread overview]
Message-ID: <CAJ=RwfahxCmC+MFc=Xh7WbmN_k=coen1SE-2E+Mq-69P0bmb6g@mail.gmail.com> (raw)
In-Reply-To: <87pow1zlgs.fsf@gnu.org>

On Fri, Feb 12, 2016 at 4:07 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> On Sun, Dec 20, 2015 at 5:34 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> ludo@gnu.org (Ludovic Courtès) skribis:
>>>
>>>>>From <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19641#16>:
>>>>
>>>> There’s another problem, though.  When a dependency is a multiple-output
>>>> package, all its outputs are added to the environment, because
>>>> ‘package->transitive-inputs’ discards the information of which output is
>>>> needed.
>>>>
>>>> So for instance, both the ‘out’ and the ‘debug’ output of Coreutils end
>>>> up being downloaded and added to the environment, even though only ‘out’
>>>> is an input.
>>>>
>>>> Now, the problem is that ‘build-derivations’ can only build *all* the
>>>> outputs of the given derivation.  This could be worked around either:
>>>>
>>>>   1. by creating a “sink” derivation, for instance with
>>>>      ‘profile-derivation’, that could refer precisely to the output(s)
>>>>      needed; not ideal.
>>>
>>> David, I think you had started looking at doing exactly this.  Do you
>>> have a preliminary patch you’d like to post?
>>>
>>> I understand you may be busy preparing the Lisp Game Jam now and I
>>> wouldn’t want to distract you from that.  ;-)  If you have something to
>>> share, I’m happy to help start from there though (says the guy who sees
>>> its ‘guix environment’ pointlessly downloading “debug” and “doc” outputs
>>> again.)
>>
>> The wip-environment-profiles branch has the code I've written thus
>> far.  I rebased it on master and resolved some conflicts in hopefully
>> the right way. :)
>>
>> When I last hacked on it I got into a fully working state AFAICT, but
>> the tests needed updating and that proved to be the most challenging
>> part.  If you're willing to finish it up, that would be awesome!
>
> It took me a while but I’ve finally finished it and pushed as 779aa00.
>
> I took a different strategy for the tests, which is to rely (in part) on
> the output of ‘guix gc --references’ to determine whether the profile
> contains all we need.

Thank you!  I'm excited that this is finally in master.

- Dave

      reply	other threads:[~2016-02-12 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 18:24 bug#19816: 'guix environment' always downloads all the outputs of dependencies Ludovic Courtès
2015-12-20 22:34 ` Ludovic Courtès
2015-12-21 17:21   ` Thompson, David
2015-12-21 21:31     ` Ludovic Courtès
2016-02-12 21:07     ` Ludovic Courtès
2016-02-12 21:37       ` Thompson, David [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='CAJ=RwfahxCmC+MFc=Xh7WbmN_k=coen1SE-2E+Mq-69P0bmb6g@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=19816-done@debbugs.gnu.org \
    --cc=davet@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).