Re: [R-SIG-Mac] [Rd] My first package
On Mon, Jan 20, 2014 at 9:58 AM, Federico Calboli wrote: [...] > I do that *with the current release of R* and I never had an issue > whatsoever. Incidentally the words 'This should be done with the current > version of R-devel (or if that is not possible, current R-patched or the > current release of R' translate in plainspeak 'run R CMD check --as-cran > with whatever version of R provided it's not outdated'. That's an interesting "translation". Are you a CRAN maintainer? I guess you were just lucky so far. Most packages are small and not affected by changes between R-release and R-devel. But some of them are. Also, R-devel typically has more rigorous package checks than R-release. My package was delayed several times because it did not pass checks in R-devel (it did in R-release). I guess this happened to other packages as well, hence the sentence above was included in the policies. Gabor [[alternative HTML version deleted]] ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On Mon, Jan 20, 2014 at 10:34 AM, Federico Calboli wrote: [...] > > That's as interesting as the English language makes it -- please note of > the expression 'should' as opposed to 'must', and the list of three options > of R versions. > Well, my interpretation is that package maintainers are expected to make an effort and check the package with R-devel. If they cannot for some reason, e.g. they cannot install R-devel, then R-patched or R-release. > Are you a CRAN maintainer? > > I maintain two packages on CRAN, if that's what you're asking. No, that's not what I am asking. > > > I guess you were just lucky so far. Most packages are small and not > affected by changes between R-release and R-devel. But some of them are. > > > > Also, R-devel typically has more rigorous package checks than R-release. > > Does it? > E.g. in current R-devel: * R CMD check reports namespaces imported _via_ ::: calls, including where this is unnecessary because :: would do or the code is in the namepace being imported from. (http://stat.ethz.ch/R-manual/R-devel/NEWS) > My package was delayed several times because it did not pass checks in > R-devel (it did in R-release). I guess this happened to other packages as > well, hence the sentence above was included in the policies. > > I presume that the issue is this: some packages are written solely in R, > hence, unless one uses a particular and outdated syntax, there are no > differences between R-devel and and R-current, whereas packages that call > C/C++/Fortran code are subject to the vagaries of compilers and operating > systems, and using R-devel should help future proofing the package, while > maintaing compatibility with R-current. > Partially, but not completely. You can have issues with R code (or even the manual!) as well, see above: if you have an unneeded ::: in your R code, then it will pass the check in R-release, but not in R-devel. Or, this one was new in R-3.0.2: * R CMD check --as-cran checks the line widths in usage and examples sections of the package Rd files. So again, back when this was only included in R-devel, your package with too long lines in the manual page examples passed the check on R-release, but not on R-devel. Gabor [[alternative HTML version deleted]] ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On Mon, Jan 20, 2014 at 4:31 AM, Federico Calboli wrote: [...] > Is it? this is news to me. I have a grand total of 2 packages up and I > never ever used R-devel, and never ever had a problem, had a report of a > problem or had a note from CRAn about my packages not being ok because I > built them with R-relase (or whatever it might be called) and not R-devel. > >From the CRAN repository policy, that you also read and agreed to: "Please ensure that R CMD check --as-cran has been run on the tarball to be uploaded before submission. This should be done with the current version of R-devel (or if that is not possible, current R-patched or the current release of R.)" Gabor [...] [[alternative HTML version deleted]] ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On Jan 20, 2014, at 10:34 AM, Federico Calboli wrote: > > On 20 Jan 2014, at 15:15, Gábor Csárdi wrote: > >> On Mon, Jan 20, 2014 at 9:58 AM, Federico Calboli >> wrote: >> [...] >> I do that *with the current release of R* and I never had an issue >> whatsoever. Incidentally the words 'This should be done with the current >> version of R-devel (or if that is not possible, current R-patched or the >> current release of R' translate in plainspeak 'run R CMD check --as-cran >> with whatever version of R provided it's not outdated'. >> >> That's an interesting "translation". > > That's as interesting as the English language makes it -- please note of the > expression 'should' as opposed to 'must', and the list of three options of R > versions. > Yes, in that order. Note also *if that is not possible*. The whole point is that the check on CRAN *will* be run against R-devel which is what you have to satisfy. By not using R-devel you're taking the chance of not passing some tests and creating extra work for the CRAN maintainers to give you the output that you could have gotten yourself and request fixes - that's why it says "should". Given the number of package submissions, the effect of people that choose to ignore the rules compounds and thus creates a significant preventable workload which the above rule attempts to minimize. >> Are you a CRAN maintainer? > > I maintain two packages on CRAN, if that's what you're asking. > >> >> I guess you were just lucky so far. Most packages are small and not affected >> by changes between R-release and R-devel. But some of them are. >> >> Also, R-devel typically has more rigorous package checks than R-release. > > Does it? > Yes, often. >> My package was delayed several times because it did not pass checks in >> R-devel (it did in R-release). I guess this happened to other packages as >> well, hence the sentence above was included in the policies. > > I presume that the issue is this: some packages are written solely in R, > hence, unless one uses a particular and outdated syntax, there are no > differences between R-devel and and R-current, Wrong > whereas packages that call C/C++/Fortran code are subject to the vagaries of > compilers and operating systems, and using R-devel should help future > proofing the package, while maintaing compatibility with R-current. > You're asked to use R-devel and on OS X it's readily available including binary package dependencies. Cheers, Simon ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On 20 Jan 2014, at 15:15, Gábor Csárdi wrote: > On Mon, Jan 20, 2014 at 9:58 AM, Federico Calboli > wrote: > [...] > I do that *with the current release of R* and I never had an issue > whatsoever. Incidentally the words 'This should be done with the current > version of R-devel (or if that is not possible, current R-patched or the > current release of R' translate in plainspeak 'run R CMD check --as-cran with > whatever version of R provided it's not outdated'. > > That's an interesting "translation". That's as interesting as the English language makes it -- please note of the expression 'should' as opposed to 'must', and the list of three options of R versions. > Are you a CRAN maintainer? I maintain two packages on CRAN, if that's what you're asking. > > I guess you were just lucky so far. Most packages are small and not affected > by changes between R-release and R-devel. But some of them are. > > Also, R-devel typically has more rigorous package checks than R-release. Does it? > My package was delayed several times because it did not pass checks in > R-devel (it did in R-release). I guess this happened to other packages as > well, hence the sentence above was included in the policies. I presume that the issue is this: some packages are written solely in R, hence, unless one uses a particular and outdated syntax, there are no differences between R-devel and and R-current, whereas packages that call C/C++/Fortran code are subject to the vagaries of compilers and operating systems, and using R-devel should help future proofing the package, while maintaing compatibility with R-current. BW F > > Gabor signature.asc Description: Message signed with OpenPGP using GPGMail ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On 20 Jan 2014, at 14:51, Gábor Csárdi wrote: > On Mon, Jan 20, 2014 at 4:31 AM, Federico Calboli > wrote: > [...] > Is it? this is news to me. I have a grand total of 2 packages up and I > never ever used R-devel, and never ever had a problem, had a report of a > problem or had a note from CRAn about my packages not being ok because I > built them with R-relase (or whatever it might be called) and not R-devel. > > From the CRAN repository policy, that you also read and agreed to: To be honest I have little time to read the byzantine requirements of the policies but > > "Please ensure that R CMD check --as-cran has been run on the tarball to be > uploaded before submission. This should be done with the current version of > R-devel (or if that is not possible, current R-patched or the current release > of R.)" I do that *with the current release of R* and I never had an issue whatsoever. Incidentally the words 'This should be done with the current version of R-devel (or if that is not possible, current R-patched or the current release of R' translate in plainspeak 'run R CMD check --as-cran with whatever version of R provided it's not outdated'. F > > Gabor > > [...] signature.asc Description: Message signed with OpenPGP using GPGMail ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Re: [R-SIG-Mac] [Rd] My first package
On Jan 18, 2014, at 9:31 AM, Axel Urbiz wrote: > Hi All, > > > I'm planning to submit my first package to R, and although I read all the > documentation, I'm not very clear on the following 2 items, from which I'd > appreciate your guidance: > > > 1)I understand it is suggested to use the R dev version to build the > package. Which one specifically should I use to build a package on a Mac > OS? How about package dependencies, which version should I install on the R > dev version (and where should I get them)? > You can get latest R-devel builds for Mac OS X from http://r.research.att.com and the same is true for binary packages for R-devel - simply use http://r.research.att.com as the repository (in fact most CRAN mirrors should work as well). Cheers, Simon > 2) Not sure if this one belongs to this list. Does licensing follow the > logic of "inheritance" (i.e. if all the package dependencies of my package > are "GPL-2 | GPL-3", does my package need to use the same license agreement? > > > > Thanks! > > Axel. > > [[alternative HTML version deleted]] > > __ > [email protected] mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > ___ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
