From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] profiles: Generate GHC's package database cache.
Date: Sun, 05 Apr 2015 22:06:04 +0200 [thread overview]
Message-ID: <87mw2mcpcj.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPNOoT7mfc7B7O4vcCSdagbQJE1WFQdVbiRikLOsu3T54w@mail.gmail.com> (Federico Beffa's message of "Sat, 4 Apr 2015 23:10:57 +0200")
Federico Beffa <beffa@ieee.org> skribis:
> From dfe3b875267731006512b8a9803aaa56f07db12e Mon Sep 17 00:00:00 2001
> From: Federico Beffa <beffa@fbengineering.ch>
> Date: Sat, 4 Apr 2015 22:51:13 +0200
> Subject: [PATCH] profiles: Generate GHC's package database cache.
>
> * guix/profiles.scm (ghc-package-cache-file): New procedure.
> (profile-derivation): Add 'ghc-package-cache?' keyword argument. If true
> (the default), add the result of 'ghc-package-cache-file' to 'inputs'.
> * guix/scripts/package.scm (guix-package)[process-actions]: Pass
> #:ghc-package-cache? to 'profile-generation'.
> * tests/packages.scm ("--search-paths with pattern"): Likewise.
> * tests/profiles.scm ("profile-derivation"): Likewise.
LG, but...
> On Sun, Apr 5, 2015 at 7:21 AM, Mark H Weaver <mhw@netris.org> wrote:
>> I believe this will require GHC to build *any* non-empty profile. Since
>> GHC is only available on Intel platforms, this will break profile
>> building on MIPS and ARM.
>>
>> Even on Intel platforms, I don't want to have to install GHC to build
>> profiles that don't contain any Haskell packages, especially since it
>> involves trusting the upstream binaries from GHC.
All good points.
> Good point. Would this check be satisfactory for you?
>
> ;; Don't depend on GHC when there's nothing to do.
> (if (any (cut string-prefix? "ghc" <>)
> (map manifest-entry-name (manifest-entries manifest)))
> (gexp->derivation "ghc-package-cache" build
> #:modules '((guix build utils))
> #:local-build? #t)
> (gexp->derivation "ghc-package-cache" #~(mkdir #$output))))
I think that would do.
Eventually we could think of more sophisticated way to determine whether
to trigger a given “hook” (info-dir, ca-certificates, ghc.) Perhaps
this ‘ghc-package-cache-file’ procedure could be added as an
‘environment-hook’ field of the ghc package and it would be triggered
iff GHC is installed. (This approach would work well for GHC, but not
for info-dir or ca-certificates, though.)
>> What if I want to use Hugs instead, or some other Haskell implementation
>> that is capable of being bootstrapped from source code. Is GHC the only
>> tool that can do this job?
>
> As far as I know, the library database is compiler specific. Here we
> are handling GHC only.
I think this is fine. A similar hook could be added for Hugs if/when we
see fit and presumably they would not interfere.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-04-05 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 21:10 [PATCH] profiles: Generate GHC's package database cache Federico Beffa
2015-04-05 5:21 ` Mark H Weaver
2015-04-05 8:16 ` Federico Beffa
2015-04-05 20:24 ` Mark H Weaver
2015-04-05 20:33 ` Federico Beffa
2015-04-06 8:18 ` Federico Beffa
2015-04-06 8:24 ` Mark H Weaver
2015-04-06 8:27 ` Federico Beffa
2015-04-06 19:00 ` Ludovic Courtès
2015-04-10 12:30 ` Alexandre Héaumé
2015-04-05 20:06 ` Ludovic Courtès [this message]
2015-04-05 20:27 ` Federico Beffa
2015-04-15 21:28 ` 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=87mw2mcpcj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--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 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).