This PR is refered to #1 but I made a lot of modifications, besides to add Travis CI, so I ask you both to review and see if you agree.
In summary the changes were:
Added and configured Travis integration. The status badges in branch issue#1 are with unknown status, but this is because it needs to have at least one push to each master and devel branches. The status is OK, and all checks are passing. See https://travis-ci.org/wbonat/mcglm
To make all checks pass, I had to make some changes. The main is to add devtools, MASS, mvtnorm and tweedie to the Suggests field in the DESCRIPTION file. This was necessary since there was a warning about the vignettes not finding this packages. This is what the R Extensions manual tells to do, and in Suggests are only "optional" packages. See commit 213e6cc93 message for more details.
In the README I've changed all installation instructions to use Github, and all links to point to Github too, as I think this may be the main (and more secure) development platform we can use for now.
I've created a new download folder to host the source files (.tar.gz, .zip, and the PDF manual). This way, these files stay hosted at Github, and we do not need to ssh to our servers (we can do this anyway, but hosting at Github guarantee that the files will be available always).
At the and of the buildPkg.R there are a simple command to automate sending these files to the downloads folder after the build.
I've changed the package version number from 0.0.2 to 0.2.0. Since we are using the major.minor.patch scheme, this seems more suitable. The last digit should be changed when minor updates or bug fixes are made. And changing the middle digit only for bigger changes.
In buildPkg.R I've changed the way of installing the package from GitHub for testing. Changing the user .libPaths() can cause a lot of trouble because after that change, all the packages that were in the first position are no longer available (as it happened for me). So I included a new function: with_libpaths() from the withr package. I saw this as the only way to install a package with install_github() in another path, without modifying the .libPaths(). The downside is that we have to install devtools and all of its dependencies (a lot!) all the time. Anyway, I think this step may be optional, since this is the work of Travis now.
Please, see the commit messages for more details. But, everything seems to be working and able to merge.
@wbonat and @walmes
This PR is refered to #1 but I made a lot of modifications, besides to add Travis CI, so I ask you both to review and see if you agree.
In summary the changes were:
issue#1are with unknown status, but this is because it needs to have at least one push to eachmasteranddevelbranches. The status is OK, and all checks are passing. See https://travis-ci.org/wbonat/mcglmdevtools,MASS,mvtnormandtweedieto theSuggestsfield in theDESCRIPTIONfile. This was necessary since there was a warning about the vignettes not finding this packages. This is what the R Extensions manual tells to do, and inSuggestsare only "optional" packages. See commit 213e6cc93 message for more details.READMEI've changed all installation instructions to use Github, and all links to point to Github too, as I think this may be the main (and more secure) development platform we can use for now.downloadfolder to host the source files (.tar.gz,.zip, and the PDF manual). This way, these files stay hosted at Github, and we do not need to ssh to our servers (we can do this anyway, but hosting at Github guarantee that the files will be available always).buildPkg.Rthere are a simple command to automate sending these files to thedownloadsfolder after the build.major.minor.patchscheme, this seems more suitable. The last digit should be changed when minor updates or bug fixes are made. And changing the middle digit only for bigger changes.buildPkg.RI've changed the way of installing the package from GitHub for testing. Changing the user.libPaths()can cause a lot of trouble because after that change, all the packages that were in the first position are no longer available (as it happened for me). So I included a new function:with_libpaths()from thewithrpackage. I saw this as the only way to install a package withinstall_github()in another path, without modifying the.libPaths(). The downside is that we have to installdevtoolsand all of its dependencies (a lot!) all the time. Anyway, I think this step may be optional, since this is the work of Travis now.Please, see the commit messages for more details. But, everything seems to be working and able to merge.