Hi, I was wondering if it is possible to lock a package to a specific version of R. Dependency attribute in the package DESCRIPTION only accepts >= AFAIU (http://cran.r-project.org/doc/manuals/R-exts.html#fn-3 ) Any work around? Thanks, Mehmet LEGAL NOTICE This message is intended for the use o...{{dropped:10}}
lock a package to specific R version
5 messages · Brian Ripley, Mehmet Suzen, Uwe Ligges
On 25.10.2011 11:42, Mehmet Suzen wrote:
Hi, I was wondering if it is possible to lock a package to a specific version of R. Dependency attribute in the package DESCRIPTION only accepts>= AFAIU (http://cran.r-project.org/doc/manuals/R-exts.html#fn-3 ) Any work around?
Intervals are possible., and you can restrict them to one version as follows: Depends: R (>= 2.13.2), R (<= 2.13.2) Uwe Ligges
Thanks,
Mehmet
LEGAL NOTICE
This message is intended for the use o...{{dropped:10}}
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
On Wed, 26 Oct 2011, Uwe Ligges wrote:
On 25.10.2011 11:42, Mehmet Suzen wrote:
Hi, I was wondering if it is possible to lock a package to a specific version of R. Dependency attribute in the package DESCRIPTION only accepts>= AFAIU (http://cran.r-project.org/doc/manuals/R-exts.html#fn-3 ) Any work around?
Intervals are possible., and you can restrict them to one version as follows: Depends: R (>= 2.13.2), R (<= 2.13.2)
Or even use == The point of the footnote is that install.packages() will download a package only checking any >= requirements (and I suspect it will then install a binary version of a package). R CMD INSTALL will not install it from the sources, and library() will not load it. I don't see why you would want to do this: why would a package work with 2.13.1 and not 2.13.2, or 2.13.2 and not 2.14.0? Ranges may make sense.
Uwe Ligges
Thanks,
Mehmet
LEGAL NOTICE
This message is intended for the use o...{{dropped:10}}
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
-----Original Message----- From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] Sent: 26 October 2011 10:12 To: Uwe Ligges Cc: Mehmet Suzen; r-help at r-project.org Subject: Re: [R] lock a package to specific R version On Wed, 26 Oct 2011, Uwe Ligges wrote:
On 25.10.2011 11:42, Mehmet Suzen wrote:
Hi, I was wondering if it is possible to lock a package to a specific version of R. Dependency attribute in the package DESCRIPTION only accepts>= AFAIU
Depends: R (>= 2.13.2), R (<= 2.13.2)
Or even use ==
Dear Professor Ripley, Thank you for the reply. We are maintaining Internal R packages and build binaries for different versions of R base, ranging from 2.8.x to 2.13.x We need to prevent users using "wrong" versions, but the ones we tested. (we distribute binaries only and package source base is evolving as well) Not sure how to address this, initially I was thinking to put R version in the package version, but package version in description files only allows x.x.x format which doesn't give a room.
I don't see why you would want to do this: why would a package work with 2.13.1 and not 2.13.2, or 2.13.2 and not 2.14.0? Ranges may make sense.
Ranges would be much more sensible then "==".
Best Regards,
Mehmet
LEGAL NOTICE
This message is intended for the use o...{{dropped:10}}
On 26.10.2011 15:12, Mehmet Suzen wrote:
-----Original Message----- From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] Sent: 26 October 2011 10:12 To: Uwe Ligges Cc: Mehmet Suzen; r-help at r-project.org Subject: Re: [R] lock a package to specific R version On Wed, 26 Oct 2011, Uwe Ligges wrote:
On 25.10.2011 11:42, Mehmet Suzen wrote:
Hi, I was wondering if it is possible to lock a package to a specific version of R. Dependency attribute in the package DESCRIPTION only accepts>= AFAIU
Depends: R (>= 2.13.2), R (<= 2.13.2)
Or even use ==
Dear Professor Ripley, Thank you for the reply. We are maintaining Internal R packages and build binaries for different versions of R base, ranging from 2.8.x to 2.13.x We need to prevent users using "wrong" versions, but the ones we tested. (we distribute binaries only and package source base is evolving as well) Not sure how to address this, initially I was thinking to put R version in the package version, but package version in description files only allows x.x.x format which doesn't give a room.
No, you can have more, if you really want to.
I don't see why you would want to do this: why would a package work with 2.13.1 and not 2.13.2, or 2.13.2 and not 2.14.0? Ranges may make sense.
Ranges would be much more sensible then "==".
Do go ahead with my suggestion. Best wishes, Uwe
Best Regards,
Mehmet
LEGAL NOTICE
This message is intended for the use o...{{dropped:10}}
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.