On 24.03.2012 19:31, Simon Urbanek wrote:
On Mar 24, 2012, at 12:43 PM, Duncan Murdoch wrote:
On 12-03-24 10:53 AM, Uwe Ligges wrote:
On 24.03.2012 06:58, Daniel Nordlund wrote:
-----Original Message-----
From: Dan Tenenbaum [mailto:dtene...@fhcrc.org]
Sent: Friday, March 23, 2012 5:48 PM
To: Daniel Nordlund
Cc: r-devel@r-project.org
Subject: Re: [Rd] Missing Windows binary for R-2.15RC?
On Fri, Mar 23, 2012 at 4:52 PM, Daniel Nordlund
<djnordl...@frontier.com> wrote:
-----Original Message-----
From: r-devel-boun...@r-project.org [mailto:r-devel-bounces@r-
project.org]
On Behalf Of Dan Tenenbaum
Sent: Friday, March 23, 2012 12:21 PM
To: r-devel@r-project.org
Subject: [Rd] Missing Windows binary for R-2.15RC?
Hi,
The page
http://cran.r-project.org/bin/windows/base/rtest.html
has a link to:
http://cran.r-project.org/bin/windows/base/R-2.15.0rc-win.exe
However, clicking on that link gives a 404 "Object not found' error.
FYI.
Dan
I experienced the same error you did using the link you provided.
However, if you use the CRAN mirror hosted by YOUR organization, you can
get the file. :-)
I don't think so:
http://cran.fhcrc.org/bin/windows/base/R-2.15.0rc-win.exe
gives me a 404 as well.
Dan
I didn't look closely enough at what you were asking for (RC versus beta).
R-2.15RC may not have been up-loaded yet. However, I just downloaded it from
the original link that was posted, so it appears to be available now.
It may have happened that the scripts generated the webpages before the
binary was built and checked (since "beta" became "rc" yesterday).
Yes, they need manual tweaking at the conversion, and I did it after the first
upload.
If this happens again (which is pretty likely), you can manually download the previous version by editing the URL to
put in "alpha" in place of "beta", or "beta" in place of "rc".
... or have a fixed name instead (on OS X we just use 2.15-branch which is
unambiguous). For the record I find it extremely annoying that even the
installation target name changes in the installer - I keep having to change it
to R-2.15 all the time, because I don't see why you would want to have
alpha/beta/rc/release of the same R version installed in separate directories
by default - but that may be just me ;). To a lesser degree the same applies
to patch versions, but since those are released I could see an argument for
that, even though in practice I think it is not useful either (because
typically you just want to upgrade and not another copy).
I install it to the same location anyway, but I think it is also a good
idea to indicate we have a progress in the prerelerase version and make
it easy to distinguish release / prerelease versions for users.
Adapting the script won't be too hard, because - as reported to Duncan
in a private message already - we also have R and Rtools installed and
do not need to rely entirely on cmd.exe.
Uwe
Cheers,
Simon
I'd like to have this handled automatically as it was in the past, but I don't
know the Windows CMD script language well enough to do it. If any experts want
to volunteer to fix this (I think you need to create a batch script variable
from the suffix in a filename), please write to me offline.
Duncan Murdoch
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
