Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

Coverage of the database #52

Open
maelle opened this issue Sep 18, 2018 · 4 comments
Open

Coverage of the database #52

maelle opened this issue Sep 18, 2018 · 4 comments

Comments

@maelle
Copy link
Member

maelle commented Sep 18, 2018

Maybe something you've already done? If not, could this be useful?

Idea: parsing all SystemRequirements fields of CRAN packages and seeing how many of them map to an entry of the database. Not sure where the result could be published, but it could be used as a reminder to maintainers (interested in this) to add an entry to the database when needed?

@gaborcsardi
Copy link
Contributor

http://crandb.r-pkg.org/-/sysreqs?keys=[%22curl%22,%22xml2%22]

{
"curl": "libcurl: libcurl-devel (rpm) or\nlibcurl4-openssl-dev (deb).",
"xml2": "libxml2: libxml2-dev (deb), libxml2-devel (rpm)"
}

Missing ones: https://sysreqs.r-hub.io/missing

@gaborcsardi
Copy link
Contributor

Maybe the missing ones could have the maintainer as well? And we could publish it daily? Recalculating it takes some time.... I am not sure if I want to email people about these, probably not.

@maelle
Copy link
Member Author

maelle commented Sep 19, 2018

Wow so cool that there's a direct URL for the missing ones!

You could email webdriver & shinytest authors 😸

I'm wondering whether there could be a link to that page in the README, with a note "is your package in this list? contribute to the database!". 🤔 And/or a blog post (an R-hub blog?) about system dependencies in general, with this database in particular. In rOpenSci development guide, we refer authors to this README.

@gaborcsardi
Copy link
Contributor

You could email webdriver & shinytest authors 😸

LOL.

Good idea about the link, but this list is assembled on the fly, and this is costly and heavy on the sysreqs machine, so I don't want to link to it just yet. I would need to cache it first. Also, if we link to it, then it should be HTML, not a JSON dump, so it will be a different API end point.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants