Skip to content
Prev 43066 / 63424 Next

[patch] giving library() a 'version' argument

On 12-04-11 11:28 AM, Ken Williams wrote:
I don't really see the need for this.  Packages already have a scheme 
for requiring a particular version of a package, so this would only be 
useful in scripts run outside of packages.  But what if your script 
requires a particular (perhaps obsolete) version of a package?  This 
change only puts a lower bound on the version number, and version 
requirements can be more elaborate than that.

I think my advice would be:

1.  Put your code in a package, and use the version specifications there.

2.  If you must write it in a script, then put a version test at the 
top, using packageVersion().

Duncan Murdoch