I have a package on CRAN and now have a modest update that's passing build
checks on R-forge.
Is there a mechanism on R-forge for updating an existing CRAN package,
analogous to the 'submit to cran' link on the R-forge package page, or should I
just follow the instructions at
http://cran.r-p
On 12-10-01 7:38 AM, S Ellison wrote:
I have a package on CRAN and now have a modest update that's passing build
checks on R-forge.
Is there a mechanism on R-forge for updating an existing CRAN package,
analogous to the 'submit to cran' link on the R-forge package page, or should I
just follo
On 1 October 2012 at 12:38, S Ellison wrote:
| I have a package on CRAN and now have a modest update that's passing build
checks on R-forge.
|
| Is there a mechanism on R-forge for updating an existing CRAN package,
analogous to the 'submit to cran' link on the R-forge package page, or should
On 10/1/2012 4:47 AM, Duncan Murdoch wrote:
On 12-10-01 7:38 AM, S Ellison wrote:
I have a package on CRAN and now have a modest update that's passing
build checks on R-forge.
Is there a mechanism on R-forge for updating an existing CRAN
package, analogous to the 'submit to cran' link on the
Yes, the button is still there if you are logged in and unhide it. (You
probably also need the appropriate developer permission.) Beware that
R-forge needs to indicate the package build status is current, but also,
if you have just made svn updates it may falsely indicate current. Check
the rev
On 10/1/2012 9:30 AM, Paul Gilbert wrote:
Yes, the button is still there if you are logged in and unhide it.
(You probably also need the appropriate developer permission.) Beware
that R-forge needs to indicate the package build status is current,
but also, if you have just made svn updates it m
Hi,
In the situation below the note issued by the dispatch algo doesn't
seem right:
setClass("A", representation(stuff="complex"))
setAs("ANY", "A", function(from) new("A", stuff=as.complex(from)))
> as(6, "A")
An object of class "A"
Slot "stuff":
[1] 6+0i
> as(6L, "A")
Note: M