Skip to content
Prev 42943 / 63421 Next
Original Raw

CRAN policies

Paul Gilbert 
An associated problem, for the wish list, is that it would be nice for 
package developers to have a way to automatically distinguish between 
NOTEs that can usually be ignored (e.g. a package suggests a package 
that is not available for cross reference checks - I have several case 
where the suggested package depends on the package being built, so this 
NOTE occurs all the time), and NOTEs that are really pre-WARNINGS, so 
that one can flag these and spend time fixing them before they become a 
WARNING or ERROR. Perhaps two different kinds of notes?

(And, BTW, having been responsible for a certain amount of the
   >[*] Since answering several emails a day about why their
   >results were different was taking up far too much time.
I think --as-cran is great.)

Paul
On 12-03-27 02:19 PM, Uwe Ligges wrote:

Thread (32 messages)

Brian Ripley CRAN policies Mar 27 Paul Gilbert CRAN policies Mar 27 Uwe Ligges CRAN policies Mar 27 Gabor Grothendieck CRAN policies Mar 27 Paul Gilbert CRAN policies Mar 27 Uwe Ligges CRAN policies Mar 27 Uwe Ligges CRAN policies Mar 27 Brian Ripley CRAN policies Mar 27 Gabor Grothendieck CRAN policies Mar 27 Jeff Ryan CRAN policies Mar 27 Uwe Ligges CRAN policies Mar 27 Jeff Ryan CRAN policies Mar 27 Gabor Grothendieck CRAN policies Mar 27 Paul Gilbert CRAN policies Mar 27 Yihui Xie CRAN policies Mar 27 Hadley Wickham CRAN policies Mar 27 Hadley Wickham CRAN policies Mar 27 Murray Stokely CRAN policies Mar 27 jing hua zhao CRAN policies Mar 28 Uwe Ligges CRAN policies Mar 28 Uwe Ligges CRAN policies Mar 28 Uwe Ligges CRAN policies Mar 28 Gabor Grothendieck CRAN policies Mar 28 Uwe Ligges CRAN policies Mar 28 Thomas Lumley CRAN policies Mar 28 Gabor Grothendieck CRAN policies Mar 29 Brian G. Peterson CRAN policies Mar 29 Peter Dalgaard CRAN policies Mar 29 Dirk Eddelbuettel CRAN policies Mar 29 Spencer Graves CRAN policies Mar 29 Claudia Beleites CRAN policies Mar 30 Paul Gilbert R-forge --as-cran Mar 30