From: Robert Greener <me@r0bert.dev>
To: gentoo-guru@lists.gentoo.org
Cc: Robert Greener <me@r0bert.dev>
Subject: [gentoo-guru] [RFC PATCH 0/3] eclass/R-packages: improvements
Date: Tue, 5 Jul 2022 07:15:59 +0000 [thread overview]
Message-ID: <010b0181cd374297-547f5cd8-3342-4193-970c-422efcd8fa0b-000000@eu-west-2.amazonses.com> (raw)
Hello,
This is very much a RFC on some improvements to the R-packages eclass.
There is currently a problem with the SRC_URI in that it will only work
with up-to-date packages, for example dplyr 1.0.9 will work, however,
dplyr 1.0.8 will not. This significantly increases the maintenance
burden of dev-R/*, as all packages must be up-to-date at all times, in
order for them to build.
To fix this, I propose to change SRC_URI to use either src/contrib or
src/contrib/Archive (where old packages will be). However, the drawback
of this is that we only use the main CRAN. As there are many mirrors to
search, it would be impractial to search them all before searching the
archive.
I also suggest 2 further changes. Firstly, replacing _ with . in the PN
in SRC_URI and HOMEPAGE. This is already done elsewhere in the eclass,
and would mean that these don't need to be overrided in the ebuild.
Finally, I suggest adding a variable CRAN_PV, that defaults to PV, for
the case where the version is something like "1.2-24". This is used in
SRC_URI, meaning that this doesn't need to be overrided in the ebuild.
--
Robert
Robert Greener (3):
eclass/R-packages: Use src/contrib or src/contrib/Archive from main
CRAN
eclass/R-packages: substitute _ with . in SRC_URI and HOMEPAGE
eclass/R-packages: Add CRAN_PV
eclass/R-packages.eclass | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.35.1
next reply other threads:[~2024-11-24 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 7:15 Robert Greener [this message]
2022-07-06 0:24 ` [gentoo-guru] [RFC PATCH 0/3] eclass/R-packages: improvements Alessandro Barbieri
2022-07-06 9:08 ` Robert Greener
2022-07-06 11:21 ` Anna “CyberTailor”
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=010b0181cd374297-547f5cd8-3342-4193-970c-422efcd8fa0b-000000@eu-west-2.amazonses.com \
--to=me@r0bert.dev \
--cc=gentoo-guru@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox