Skip to content

[R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

4 messages · Marius Hofert, Hugh Parsonage, Dirk Eddelbuettel

#
okay, so (afaik) this is just a github repos which contains an exact
copy of the github version of the problematic package (here: loon). I
would then (at some future point) just do a pull to get the latest
source, create the package from there and essential refer to it from
Additional_repositories via: "Additional_repositories:
https://myuser.github.io/drat"

(so if CRAN would actually archive packages directly to a github
repos, one would not need to create a separate copy/repos'es... :-) ).

Btw, at the bottom of http://eddelbuettel.github.io/drat/DratFAQ.html
you refer to 'wikipediatrend' as an example for how to use
Additional_repositories. The link points to
https://github.com/petermeissner/wikipediatrend/blob/master/DESCRIPTION
which does not contain such a line. Might be better to just refer to
your R paper.

Cheers,
M
#
On 25 February 2018 at 15:00, Marius Hofert wrote:
| okay, so (afaik) this is just a github repos which contains an exact
| copy of the github version of the problematic package (here: loon). I

Be very careful with terminology here:

 -- "github repo" is to most people a source code repo
 -- drat uses github and its "automatic webserver" to provide an "R repo", ie
    a repository for R packages (ie .tar.gz, binaries for macOS and windows
    work too if you build them).

I have long joked that I wrote more documentation than code for drat, and it
still confused the hell out of people.  But there are numerous vignettes, a
useR talk I have and of course the long and very detailed paper.

Dirk
#
Not to mention a drat repository you can just fork with a single click!
On Mon, 26 Feb 2018 at 3:25 am, Dirk Eddelbuettel <edd at debian.org> wrote:

            

  
  
#
On 25 February 2018 at 16:45, Hugh Parsonage wrote:
| Not to mention a drat repository you can just fork with a single click!

Yes, very easy -- but marginally expensive as you get the content (ie drat
code history) mirrored.  If you're at ease with git you can do it all by hand
too.  We still use the gh-pages branch for the webserver though (but now
support a contributed option to override that default target branch).

The other good thing that there are a number of public drat repos so you can
always poke around.

Dirk