Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Submit to CRAN? #6

Open
maurolepore opened this issue Aug 18, 2017 · 1 comment
Open

Submit to CRAN? #6

maurolepore opened this issue Aug 18, 2017 · 1 comment

Comments

@maurolepore
Copy link
Contributor

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.

@maurolepore maurolepore changed the title Submit to cran? Submit to CRAN Aug 18, 2017
@maurolepore maurolepore changed the title Submit to CRAN Submit to CRAN? Aug 18, 2017
@maurolepore
Copy link
Contributor Author

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().

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

No branches or pull requests

1 participant