From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: m8r-y0v7u9@mailinator.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] r: make and install info files
Date: Tue, 30 Jun 2015 16:40:21 +0200 [thread overview]
Message-ID: <idj7fqli7je.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20150630085317.ADF86D56E8@emkei.cz>
Hi,
> * gnu/packages/statistics.scm (r)[arguments]: make and install info files
>
> diff --git a/gnu/packages/statistics.scm b/gnu/packages/statistics.scm
> index 0b9e081..0dfe25d 100644
> --- a/gnu/packages/statistics.scm
> +++ b/gnu/packages/statistics.scm
> @@ -63,7 +63,23 @@
> 'check 'set-timezone
> ;; Some tests require the timezone to be set.
> (lambda _ (setenv "TZ" "UTC"))
> - %standard-phases)
> + (alist-cons-after
> + 'install 'install-info
> + (lambda* (#:key inputs outputs #:allow-other-keys)
> + ;; Install the Info manual, unless Texinfo is missing.
> + (or (not (assoc-ref inputs "texinfo"))
This seems a bit odd. We have control over whether "texinfo" is among
the inputs, so I don't think this check is useful.
> + (let ((out (assoc-ref outputs "out")))
> + (and (zero? (system* "make" "info"))
> + (let ((infodir (string-append out "/share/info")))
> + (mkdir-p infodir)
> + (chdir "./doc/manual")
> + (for-each (lambda (info)
> + (copy-file
> + info
> + (string-append infodir "/" info)))
> + (find-files "." "\\.info$"))
> + #t)))))
> + %standard-phases))
> #:configure-flags
> '("--with-blas"
> "--with-lapack"
I also wonder if maybe we should switch to using the (modify-phases ...)
syntax before adding new phases. This would avoid future
indentation-only modifications.
What do you think?
~~ Ricardo
next prev parent reply other threads:[~2015-06-30 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 8:53 [PATCH] r: make and install info files m8r-y0v7u9
2015-06-30 14:40 ` Ricardo Wurmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-01 11:31 m8r-y0v7u9
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=idj7fqli7je.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=m8r-y0v7u9@mailinator.com \
/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.