unofficial mirror of guix-devel@gnu.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 5/6] gnu: mit-scheme: Generate and install documentation.
Date: Tue, 05 Jan 2016 23:13:23 +0100	[thread overview]
Message-ID: <87k2nnk73w.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPMtvKf8ShfbtZdbDcwE+ADw+qQGGsXhfwUNGu5r7BU4Nw@mail.gmail.com> (Federico Beffa's message of "Wed, 30 Dec 2015 18:33:33 +0100")

Federico Beffa <beffa@ieee.org> skribis:

> From 5c2be0d7d628ba27ac1360cc8e998de68a505b2a Mon Sep 17 00:00:00 2001
> From: Federico Beffa <beffa@fbengineering.ch>
> Date: Sun, 27 Dec 2015 19:06:37 +0100
> Subject: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.
>
> * gnu/packages/scheme.scm (mit-scheme): Convert to the 'modify-phases'
>   syntax. Add phases 'configure-doc, 'build-doc and 'install-doc. Add
>   'texlive' input.

Could you split into two patches: first ‘modify-phases’, then build doc?

I’m a bit concerned about the TeX Live dependency.  I wonder if we
should instead make a separate ‘mit-scheme-doc’ package so that people
don’t have to download/build TeX Live just to build MIT Scheme.  No
strong opinion though.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-01-05 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 17:33 [PATCH 5/6] gnu: mit-scheme: Generate and install documentation Federico Beffa
2016-01-05 22:13 ` Ludovic Courtès [this message]
2016-01-09 10:28   ` Federico Beffa
2016-01-09 18:42     ` Ludovic Courtès
2016-01-09 22:32       ` Federico Beffa
2016-01-10 18:50         ` Ludovic Courtès
2016-01-10 21:19           ` Federico Beffa
2016-01-10 23:14             ` Mathieu Lirzin
2016-01-11  8:20               ` Federico Beffa
2016-01-11  9:09             ` Ludovic Courtès
2016-01-11 11:58               ` Federico Beffa
2016-01-11 19:06                 ` Leo Famulari
2016-01-12  7:46                   ` Federico Beffa
2016-01-11 20:47                 ` 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=87k2nnk73w.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).