On 18 May 2025 at 09:23, Michael Chirico wrote:
| one thing to keep in mind for the GitHub mirror is that archived packages are
| not marked any differently, e.g.
|
| https://github.com/cran/rgeos
|
| I typically use Henrik's URLs but you need to set up some retry logic. The
| rsync approach so
one thing to keep in mind for the GitHub mirror is that archived packages
are not marked any differently, e.g.
https://github.com/cran/rgeos
I typically use Henrik's URLs but you need to set up some retry logic. The
rsync approach sounds nice, think I'll try that next time :)
On Sun, May 18, 202
Also, and while it won't help for the non-standard field in question here,
the standard fields are all compiled into what tools::CRAN_package_db()
returns. Very handy for many use cases, and possibly not as well known as it
should be.
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian
All DESCRIPTION files are available as:
https://cran.r-project.org/web/packages/{pkg}/DESCRIPTION
For example, https://cran.r-project.org/web/packages/cli/DESCRIPTION.
So, you could manually iterate over all CRAN packages and download these
files one by one. An alternative is to rsync just the D
Ah, perfect! Thanks :)
On Sun, May 18, 2025 at 07:10 Kenny, Christopher <
christopherke...@fas.harvard.edu> wrote:
> I think this is a good case for using the unofficial GitHub CRAN mirror.
> Then you can just use the search like so:
>
>
> https://github.com/search?q=org%3Acran%20%22Config%2Frext
I think this is a good case for using the unofficial GitHub CRAN mirror. Then
you can just use the search like so:
https://github.com/search?q=org%3Acran%20%22Config%2Frextendr%2Fversion%22%20&type=code
Best,
Chris
From: R-package-devel on behalf of
Josiah Par
Hi:
I often search in https://github.com/cran , each repo is a package on
CRAN. Combined with GitHub Code Search you can identify packages with
common DESCRIPTION features.
Try this link:
https://github.com/search?q=org%3Acran%20path%3ADESCRIPTION%20Config%2Frextendr%2Fversion&type=code
Hav
