Handle example data for CRAN

insightsengineering / scda.2022

An archive of synthetic CDISC data for 2022

https://insightsengineering.github.io/scda.2022/

Other

9 stars 3 forks source link

Handle example data for CRAN #71

Closed nikolas-burkoff closed 1 year ago

nikolas-burkoff commented 2 years ago

Do we want the package to be called scda.2022 or something else
The size of the package gets big quickly which makes R CND check --as-cran not happy - though see https://github.com/insightsengineering/scda/issues/98

Users just want the example data they have to work with the example code, they are not interested in archives of old data - that's only useful for test cases
It may make sense for the data to end up in scda itself which would simplify some things...

Also consider https://github.com/insightsengineering/scda.2021/issues/91

shajoezhu commented 2 years ago

I thought cran does not take data packages? Please correct me if I was wrong

nikolas-burkoff commented 2 years ago

hmm - if it doesn't then we can't submit any package which uses the data package (even in suggests)?

shajoezhu commented 2 years ago

Hi @nikolas-burkoff , yea, I think we will need to discuss about the releasing plan. From a recent conversation, i think we can push to bioconductor, which is ok for the other packages have scda to be a suggested package.

Melkiades commented 2 years ago

So the plan is to push only scda to bioconductor? Is it not complaining there? I think their checks are stricter than cran's

shajoezhu commented 1 year ago

I think we can close this issue now. As scda* families are now being decoupled from tern, we will not release scda to cran