insightsengineering/scda.2022

Handle example data for CRAN

nikolas-burkoff opened this issue · 5 comments

  • 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 insightsengineering/scda#98

image

  • 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 insightsengineering/scda.2021#91

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

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

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.

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

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