Comments (4)
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.
- using
R.version
and extracting the list elementsmajor
andminor
. If specifying for a non-system version, user can useRversion=list(major="3", minor="1.0")
- "proper" numeric version using
getRversion()
. If specifying for a non-system version, user can useRversion=R_system_version("3.1.0")
. I prefer this because comparing numeric versions is built in. - 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.
Related Issues (20)
- Suggestion: Hide dependencies for some R packages in `plot.pkgDepGraph()` HOT 2
- Use github actions instead of Travis
- Installation on R < 4.0 HOT 2
- Remove dependency on curl
- Incorrect identification of packages with checkVersions() HOT 2
- Vignette for using BioConductor needs update. HOT 3
- addLocalPackage() gives error HOT 2
- Support mac.binary.big-sur-arm64 HOT 5
- Add packages to repository from GitHub (or other remotes) HOT 1
- Rename master branch to main
- Fix R-CMD-check failures
- Installation fails due to lazy load in R 4.1.3 HOT 3
- UpdatePackages function with UNC paths HOT 1
- Don't redownload packages that are already on the repo HOT 2
- Controling arg `recursive` passed to tools::package_dependencies() HOT 1
- Why I cannot install my own package I've created? HOT 1
- miniCRAN::makeRepo downloads R-devel version of a package HOT 1
- Get ready for CRAN release v0.3 HOT 2
- Error when creating repo HOT 2
- Pass on `filters` argument to `pkgAvail()` in `makeRepo()` HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from minicran.