public inbox for gentoo-guru@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alessandro Barbieri <lssndrbarbieri@gmail.com>
To: "Anna “CyberTailor”" <cyber@sysrq.in>
Cc: gentoo-guru@lists.gentoo.org
Subject: Re: [gentoo-guru] [RFC PATCH 1/3] eclass/R-packages: Use src/contrib or src/contrib/Archive from main CRAN
Date: Thu, 7 Jul 2022 09:17:21 +0200	[thread overview]
Message-ID: <CACfyCdXCnQimMijF=waz_9h_aJxJB1ZXDKZOQ5RU67uixeJCnA@mail.gmail.com> (raw)
In-Reply-To: <YsPvFh0dLOPiZA0b@sysrq.in>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

Il giorno mar 5 lug 2022 alle ore 09:58 Anna “CyberTailor” <cyber@sysrq.in>
ha scritto:

> On 2022-07-05 07:16, Robert Greener wrote:
> > The current SRC_URI searches all the CRAN mirrors for
> > /src/contrib/${PN}_${PV}.tar.gz. This is problematic. Once a package is
> updated
> > on CRAN, the package is removed from this path and moved to
> > /src/contrib/Archive/${PN}/${PN}_${PV}.tar.gz. The effect of this is
> > that once a package goes out-of-date on CRAN, the ebuild will no longer
> > build. This significantly increases the maintenance burden of dev-R/*
> > packages, as it requires that they be up-to-date at all times.
> >
> > The proposal here, is to use just the main CRAN, so that every mirror
> > doesn't have to be searched, to search the main repo, and then the
> > archive. (also, some CRAN mirrors seem misconfigured and return a html
> > document if the package is not found at
> > /src/contrib/${PN}_${PV}.tar.gz). This means that if the package is
> > out-of-date it will still build.
> >
> > Signed-off-by: Robert Greener <me@r0bert.dev>
> > ---
> >  eclass/R-packages.eclass | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/eclass/R-packages.eclass b/eclass/R-packages.eclass
> > index aed8cce84..dd6b69933 100644
> > --- a/eclass/R-packages.eclass
> > +++ b/eclass/R-packages.eclass
> > @@ -21,7 +21,10 @@ esac
> >
> >  EXPORT_FUNCTIONS src_unpack src_prepare src_configure src_compile
> src_install pkg_postinst
> >
> > -SRC_URI="mirror://cran/src/contrib/${PN}_${PV}.tar.gz"
> > +SRC_URI="
> > +     https://cran.r-project.org/src/contrib/${PN}_${PV}.tar.gz
> > +
> https://cran.r-project.org/src/contrib/Archive/${PN}/${PN}_${PV}.tar.gz
> > +"
>
> Multiple SRC_URI doesn't work as fallback. You need a custom src_fetch
> function instead.
>
>
I like this idea, any downsides?

[-- Attachment #2: Type: text/html, Size: 2683 bytes --]

  reply	other threads:[~2024-11-24 22:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220705071539.2463760-1-me@r0bert.dev>
2022-07-05  7:16 ` [gentoo-guru] [RFC PATCH 2/3] eclass/R-packages: substitute _ with . in SRC_URI and HOMEPAGE Robert Greener
2022-07-06  0:49   ` Anna “CyberTailor”
2022-07-05  7:16 ` [gentoo-guru] [RFC PATCH 1/3] eclass/R-packages: Use src/contrib or src/contrib/Archive from main CRAN Robert Greener
2022-07-05  7:58   ` Anna “CyberTailor”
2022-07-07  7:17     ` Alessandro Barbieri [this message]
2022-07-08 13:09       ` Robert Greener
2022-07-05  7:16 ` [gentoo-guru] [RFC PATCH 3/3] eclass/R-packages: Add CRAN_PV Robert Greener
2022-07-06 12:21 ` [gentoo-guru] [RFC PATCH v2 0/4] eclass/R-packages: improvements Robert Greener
2022-07-06 12:21   ` [gentoo-guru] [RFC PATCH v2 1/4] eclass/R-packages: Add CRAN_PV Robert Greener
2022-07-11  5:04     ` [gentoo-guru] " Alessandro Barbieri
2022-07-06 12:21   ` [gentoo-guru] [RFC PATCH v2 2/4] eclass/R-packages: Add CRAN_PN variable Robert Greener
2022-07-06 12:21   ` [gentoo-guru] [RFC PATCH v2 3/4] eclass/R-packages: Add CRAN_UPD_DATE and use MRAN Robert Greener
2022-07-06 12:21   ` [gentoo-guru] [RFC PATCH v2 4/4] eclass/R-packages: Add Robert Greener (myself) as author Robert Greener
2022-07-06 12:32   ` [gentoo-guru] [RFC PATCH v2 0/4] eclass/R-packages: improvements Anna “CyberTailor”
2022-07-11  5:06   ` [gentoo-guru] " Alessandro Barbieri
2022-07-12 12:06   ` Robert Greener

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='CACfyCdXCnQimMijF=waz_9h_aJxJB1ZXDKZOQ5RU67uixeJCnA@mail.gmail.com' \
    --to=lssndrbarbieri@gmail.com \
    --cc=cyber@sysrq.in \
    --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