From: Kyle Andrews <kyle.c.andrews@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 36805@debbugs.gnu.org
Subject: [bug#36805] Small patch to remove TODO for (@@ (guix build-system r) bioconductor-uri)
Date: Fri, 26 Jul 2019 00:17:05 -0400 [thread overview]
Message-ID: <8a97ec5ed0d1f657731c22593a1f6696af2434dc.camel@gmail.com> (raw)
In-Reply-To: <CAJ3okZ15JPdQETN1G4xS-OGyGV97_4t+Keg0eEfpCk18ir82-g@mail.gmail.com>
On Thu, 2019-07-25 at 15:48 +0200, zimoun wrote:
> Dear,
>
> It appears to me nice---if for example one wants to create a channel
> for Bioconductor 3.6 or older.
> This eases the automation of such channel.
>
> I am using the package `cytofkit`, removed in the last release:
> https://bioconductor.org/about/removed-packages/
>
> Append strings to build the uri is not really nice.
> https://github.com/zimoun/guix-bimsb/blob/master/bimsb/packages/stagi
> ng.scm#L2895-L2941
>
> Thank you for this suggestion.
>
>
> All the best,
> simon
Hi Simon,
I find it sometimes convenient to use a modified version of the
file.path function in R to save me from myself a bit with file paths
while also adding some semantic markup. Perhaps it would also be useful
for building Guix packages? Users would then seldom have to worry about
incorrectly including trailing slashes. I created a code snippet with
my naive implementation here:
https://gitlab.com/snippets/1879185
Maybe there is already a guile library for this sort of thing?
Regards,
Kyle
next prev parent reply other threads:[~2019-07-26 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 3:13 [bug#36805] Small patch to remove TODO for (@@ (guix build-system r) bioconductor-uri) Kyle Andrews
2019-07-25 13:48 ` zimoun
2019-07-26 4:17 ` Kyle Andrews [this message]
2019-07-26 9:46 ` Ricardo Wurmus
2019-09-14 21:04 ` [bug#37404] add herbstluftwm window manager package (v0.7.2) to guix (gnu/packages/wm.scm) Kyle Andrews
2019-09-16 8:57 ` bug#37404: " 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=8a97ec5ed0d1f657731c22593a1f6696af2434dc.camel@gmail.com \
--to=kyle.c.andrews@gmail.com \
--cc=36805@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.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.