-
Notifications
You must be signed in to change notification settings - Fork 17
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
Package distribution #1
Comments
btw, I would start the release numbering now with 0.1, i.e. 0.1 is our initial release of the package. Small updates should be 0.1.0.1 ... etc. Larger updates should be 0.1.1 ... |
OK. I will remove from the repo and check the other options. Currently there is no vignette. We just cannot use any function that requires to have the model. The vignette should then pose no problem. If so, we can use the first option: installing_github. |
I set version to 0.1 |
for the devtools, you have to provide the exact location of the package, i.e. devtools::install_github("biometry/RLPJ/Rlpj", ref = "master") I just tried it, it works fine. I would suggest that we let people install the development version this way, then we don't have to tag releases all the time |
I created a vignette and there is no problem when installing form github. I will complete the installation instructions. |
Hey guys, we should find another solution for the source packages, it's not good style to have this in the repo.
First of all, I assume the reason why you do this is that otherwise the vignette doesn't build properly? Because if that wasn't a problem, you could install directly from github http://www.inside-r.org/packages/cran/devtools/docs/install_github
Secondly, the better way to distribute binaries is to do proper releases via https://help.github.com/articles/creating-releases/ - I think you can upload binaries there. We should then link to the release on the main page.
The text was updated successfully, but these errors were encountered: