R help - Feb 2014 - minor version upgrade requires library refresh?

If R changes from 3.0.1 to 3.0.2, or more generally from m.n.p to m.n.q, 
is it necessary to refresh libraries to match the version, e.g., with 
update.packages(checkBuilt=TRUE, ask=FALSE)?  The R Windows FAQ 2.8 says
"For those with a personal library (folder R\win-library\x.y of your 
home directory, R\win64-library\x.y on 64-bit builds), you will need to 
update that too when the minor version of R changes (e.g. from 3.0.2 to 
3.1.0)."

This suggests that in m.n.q n is the minor version (which would make q 
the release?), and that the minor version does not change between 3.0.1 
and 3.0.1.  But I'm not sure.

I'm interested in Unix as well as Windows.

Thanks.
Ross Boylan

	[[alternative HTML version deleted]]

On Feb 13, 2014, at 11:36 AM, Ross Boylan wrote:
> If R changes from 3.0.1 to 3.0.2, or more generally from m.n.p to m.n.q, 
> is it necessary to refresh libraries to match the version, e.g., with 
> update.packages(checkBuilt=TRUE, ask=FALSE)?  The R Windows FAQ 2.8 says
> "For those with a personal library (folder R\win-library\x.y of your 
> home directory, R\win64-library\x.y on 64-bit builds), you will need to 
> update that too when the minor version of R changes (e.g. from 3.0.2 to 
> 3.1.0)."
> 
When "n" changes you need to update any existing library.
> This suggests that in m.n.q n is the minor version (which would make q 
> the release?), and that the minor version does not change between 3.0.1 
> and 3.0.1.
Huh?

>  But I'm not sure.
> 
> I'm interested in Unix as well as Windows.
> 
> Thanks.
> Ross Boylan
> 
> 	[[alternative HTML version deleted]]
Please learn to post in plain text.

-- 

David Winsemius
Alameda, CA, USA