From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34040@debbugs.gnu.org
Subject: [bug#34040] [PATCH 2/2] import: cran: Suggest input changes.
Date: Sat, 12 Jan 2019 22:11:25 +0100 [thread overview]
Message-ID: <87ef9hoa2q.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87y37q56wy.fsf@gnu.org>
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> * guix/import/cran.scm (latest-cran-release, latest-bioconductor-release):
>> Return input-changes.
>
> LGTM!
Thank you for taking the time to review this!
>> -(define (latest-cran-release package)
>> - "Return an <upstream-source> for the latest release of PACKAGE."
>> +(define (latest-cran-release pkg)
>
> Unless there’s a name clash I think it’s OK to keep ‘package’.
There is a name clash, which I found very surprising. Take this procedure:
--8<---------------cut here---------------start------------->8---
(define (latest-cran-release package)
"Return an <upstream-source> for the latest release of the package PKG."
(define upstream-name
(package->upstream-name package))
(define meta
(fetch-description 'cran upstream-name))
(and meta
(let ((version (assoc-ref meta "Version")))
;; CRAN does not provide signatures.
(upstream-source
(package (package-name package))
(version version)
(urls (cran-uri upstream-name version))
(input-changes
(changed-inputs
package ; <– this is the value of the “package” field,
; not the value of the procedure argument.
(description->package 'cran meta)))))))
--8<---------------cut here---------------end--------------->8---
That’s why I renamed the argument to “pkg”.
--
Ricardo
next prev parent reply other threads:[~2019-01-12 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 9:11 [bug#34040] Suggest input changes when updating packages Ricardo Wurmus
2019-01-11 9:42 ` [bug#34040] [PATCH 1/2] refresh: Suggest input changes when updating Ricardo Wurmus
2019-01-11 9:42 ` [bug#34040] [PATCH 2/2] import: cran: Suggest input changes Ricardo Wurmus
2019-01-12 13:42 ` Ludovic Courtès
2019-01-12 21:11 ` Ricardo Wurmus [this message]
2019-01-12 13:40 ` [bug#34040] [PATCH 1/2] refresh: Suggest input changes when updating Ludovic Courtès
2019-01-21 21:34 ` Ludovic Courtès
2019-01-25 16:21 ` Ricardo Wurmus
2019-01-25 21:15 ` Ludovic Courtès
2019-01-25 21:48 ` Ricardo Wurmus
2019-01-26 13:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef9hoa2q.fsf@mdc-berlin.de \
--to=rekado@elephly.net \
--cc=34040@debbugs.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 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.