You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may submit this package to CRAN easily. We just need to solve the issues with non_ascii characters found in species and wood density data, or to exclude those datasets completetly. The benefit of releasing to CRAN is that users can install this package directly with install.packages("bciex"), i.e. they don't need devtools to install from github via devtools::install_github(forestgeo/bciex"). Also, if bciex lives in CRAN, it is very easy to import from any other package that needs it, allowing us to avoid duplicating data for examples. Finally, this allows using Travis for continuous integration, which otherwise fails if a package is not found.
The text was updated successfully, but these errors were encountered:
Now I still think that it'd be good to submit to CRAN but for a different reason: To reserve the name. If some other package is published on CRAN with the name bciex our users may be confused.
The other reasons I gave above I now think are not so important because we now have the package remotes which includes install_github() but is much lighter weight -- meaning that users don't need to get an entire development toolkit (devtools) to only get install_github().
We may submit this package to CRAN easily. We just need to solve the issues with non_ascii characters found in species and wood density data, or to exclude those datasets completetly. The benefit of releasing to CRAN is that users can install this package directly with install.packages("bciex"), i.e. they don't need devtools to install from github via
devtools::install_github(forestgeo/bciex")
. Also, if bciex lives in CRAN, it is very easy to import from any other package that needs it, allowing us to avoid duplicating data for examples. Finally, this allows using Travis for continuous integration, which otherwise fails if a package is not found.The text was updated successfully, but these errors were encountered: