all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] build-system: Add haskell-build-system.
Date: Thu, 02 Apr 2015 23:31:30 +0200	[thread overview]
Message-ID: <878uea43pp.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPNOLVBxwYti5ody3+uBkhg9Zv6uDvHVFLXqy-qPR-kioA@mail.gmail.com> (Federico Beffa's message of "Mon, 30 Mar 2015 18:48:17 +0200")

Federico Beffa <beffa@ieee.org> skribis:

> On Mon, Mar 30, 2015 at 10:16 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Handling it during profile creation, as you suggest, and avoiding the
>> use of a wrapper sounds preferable to me.
>
> OK, lets go for that.

Sometime we’ll have to make info-dir + cert + ghc stuff in (guix
profiles) less adhoc.

> In the mean time I've found that to generate the documentation an
> additional step is required (phase haddock; the name is also the name
> of the tool used to generate the doc). I've added a keyword argument
> #:haddock? with default value of #t and #:haddock-flags for doc
> specific flags.

Nice.

> The documentation is in the form of html files and does seems to
> require a fair amount of space. Some random examples:
>
> - mtl libs: 1.2MB / doc: 0.772MB
> - text libs: 13MB / doc: 1.7MB
> - HTTP libs: 3.9MB / doc: 0.804MB
> - network-uri: libs: 1.5MB / doc: 0.168MB
> - parsec libs: 3.1MB / doc: 1.1MB
>
> Given that I'm starting to package a bunch of libraries, do we want to
> generate a separate output for all of them?

Probably, yes.

> From 87f567c0c3c06da73bd70e2498f7829258ae7d61 Mon Sep 17 00:00:00 2001
> From: Federico Beffa <beffa@fbengineering.ch>
> Date: Fri, 27 Mar 2015 09:36:56 +0100
> Subject: [PATCH 01/22] build-system: Add haskell-build-system.
>
> * guix/build-system/haskell.scm: New file.
> * guix/build/haskell-build-system.scm: New file.

[...]

> +;; - We generate the cache when a profile is created.
> +
> +;; Code:
> +;;

“Code:” should be “attached” to the block before and followed by an
empty line.

Please push, thank you!

Ludo’.

      reply	other threads:[~2015-04-02 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  8:59 [PATCH] build-system: Add haskell-build-system Federico Beffa
2015-03-29 13:44 ` Ludovic Courtès
2015-03-29 14:00   ` Ricardo Wurmus
2015-03-29 14:45     ` Federico Beffa
2015-03-30  8:16       ` Ludovic Courtès
2015-03-30 16:48         ` Federico Beffa
2015-04-02 21:31           ` 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=878uea43pp.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 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.