Inconsistent use of Rversion argument in addPackages about minicran HOT 4 CLOSED

What's your preference for specifying Rversion? Note that all three mechanisms will work with the functions. The default is to use the current system version, but this can be overridden by the user.

1. using R.version and extracting the list elements major and minor. If specifying for a non-system version, user can use Rversion=list(major="3", minor="1.0")
2. "proper" numeric version using getRversion(). If specifying for a non-system version, user can use Rversion=R_system_version("3.1.0"). I prefer this because comparing numeric versions is built in.
3. supplying character string 3.1.2. This is obviously easiest for user to specify non-system version: Rversion="3.1.0".

from minicran.

I agree with your analysis. I don't have a strong preference, other than:

• We are consistent in the defaults for all functions
• It's easy for the user (and I agree specifying a list isn't easy)

In fact we only need the major and minor version number, e.g. "3.1".

I'll think more about this tomorrow.

from minicran.

Option 3 above is the easiest for the user, so I've gone ahead with that. We can convert to to an R_system_version under the hood to make version string comparisons.

Note that I'm only making the changes to the documentation -- the functions using Rversion (namely, twodigitRversion) will still work if specified using the other approaches.

See the 42-rversion branch, which was branched from master this morning.

from minicran.

I merged this branch 24-addPackages into dev

from minicran.