[R-pkg-devel] Are import-export-only packages allowed on CRAN?

[Richard Cotton]

One piece of feedback that I received at useR was that the assertive
package is getting too big, and should be broken down into smaller
pieces.

I want to split the functionality into assertive.base,
assertive.types, and a few others, then have the assertive package as
a virtual package (suggestions for better terminology welcomed) that
just imports and reexports the contents of the underlying pieces.

That way end-users can can still type library(assertive) and have the
same behaviour as before, and package developers who worry about
having lightweight dependencies can just use the parts that they need.

Before I do the refactoring, I wanted to check that it is OK to have a
package without any of its own content (other than vignettes) on CRAN.
Is it OK?



-- 
Regards,
Richie

Learning R
4dpiecharts.com

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Are import-export-only packages allowed on CRAN?

[Richard Cotton]

I emailed the CRAN hotline, and Kurt H's response was:

> I see no problem with this.

> (Having packages which put lots of other packages on the search path are
> a problem: but I understand you won't be doing that, and instead import
> and re-export, right?)

On 6 July 2015 at 14:36, Marc Schwartz  wrote:
>
>> On Jul 6, 2015, at 5:47 AM, Dirk Eddelbuettel  wrote:
>>
>>
>> Hi Richie,
>>
>> On 5 July 2015 at 19:17, Richard Cotton wrote:
>> | One piece of feedback that I received at useR was that the assertive
>> | package is getting too big, and should be broken down into smaller
>> | pieces.
>> |
>> | I want to split the functionality into assertive.base,
>> | assertive.types, and a few others, then have the assertive package as
>> | a virtual package (suggestions for better terminology welcomed) that
>> | just imports and reexports the contents of the underlying pieces.
>> |
>> | That way end-users can can still type library(assertive) and have the
>> | same behaviour as before, and package developers who worry about
>> | having lightweight dependencies can just use the parts that they need.
>> |
>> | Before I do the refactoring, I wanted to check that it is OK to have a
>> | package without any of its own content (other than vignettes) on CRAN.
>> | Is it OK?
>>
>> That is a pure CRAN question; maybe someone from CRAN wants to chime in or
>> else you need to ask directly.
>>
>> Greg Warnes has/had such a meta package (which I look after in Debian as a
>> still-existing-there whole and componentds), and Henrik does too.  What **I
>> think** the practice is now discouraged somewhere in WRE or CRP.  But no
>> direct reference, sorry,
>>
>> Dirk
>
>
> If you are referring to a package “bundle”, they were deprecated in R 2.10.0 
> and put into defunct status in R 2.11.0. That is from the NEWS file:
>
>   https://svn.r-project.org/R/trunk/doc/NEWS.2
>
> There is no longer any reference to them in R-Exts.
>
> Greg’s “gregmisc” bundle is no longer active on CRAN, in deference to using 
> his component packages directly.
>
>
> Regards,
>
> Marc Schwartz
>



-- 
Regards,
Richie

Learning R
4dpiecharts.com

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] Writing a portable package that imports functions only available on Windows

[Richard Cotton]

I have a package that uses win.version from the utils package.

I've made my R code safe to use across platforms, I check that the OS is
Windows before calling win.version.

The NAMESPACE file contains the line

importFrom(utils,win.version)

which causes an install failure under other OSes since that function
doesn't exist.

Can I use this platform-dependent function and still have a cross-platform
package?

Also, it seems like it would be nicer if the utils package always included
this function and returned NA with a warning on platforms other than
Windows.  Does that sound like a reasonable change?

-- 
Regards,
Richie

Learning R 
4dpiecharts.com

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] What to do when you can't reproduce CRAN R CMD check unit test failures?

[Richard Cotton]

Yesterday I uploaded a new version of the pathological package to
CRAN.  It was initially accepted but today I got a message saying that
some of the tests for the decompose_path function are failing under
Windows.

I've tested the package on a local Windows 10 machine with R-3.3.0 and
R-devel, and in Win 7 and Win 8 compatibility modes, and on Windows
Server 2012 via AppVeyor.  In all cases, all the tests pass.

I tried the CRAN win builder service today, and again, all tests pass.
http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_i386/testthat.Rout
http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_x64/testthat.Rout

The failure portion of the output I got from Uwe is as follows:

* checking tests ... ERROR
Running the tests in 'tests/testthat.R' failed.
Last 13 lines of output:
  1. Failure: decompose_path handles paths with no directory and a
single extension in the filename. (@test_decompose_path.R#42)
  2. Failure: decompose_path handles paths with no directory and a
double extension in the filename. (@test_decompose_path.R#72)
  3. Failure: decompose_path handles paths with no directory and no
extension in the filename. (@test_decompose_path.R#103)
  4. Failure: decompose_path handles filenames containing a '.' and an
extension. (@test_decompose_path.R#133)
  5. Failure: decompose_path handles the current directory as '.'.
(@test_decompose_path.R#221)
  6. Failure: decompose_path handles the parent directory as '..'.
(@test_decompose_path.R#236)
  7. Failure: decompose_path handles files inside '.'.
(@test_decompose_path.R#251)
  8. Failure: decompose_path works with a character vector input.
(@test_decompose_path.R#321)
  9. Failure: decompose_path works with a factor input.
(@test_decompose_path.R#333)
  1. ...


Since this isn't hugely informative as to the problem, I'd like
general advice on how I can diagnose a failing test when I can't
reproduce it.

It would also be useful if anyone can run R CMD check and see if they
find test failures.

The CRAN release is here (the problematic version is 0.0-8):
https://cran.r-project.org/web/packages/pathological

and the github version is currently in the same state, available here:
https://github.com/richierocks/pathological

-- 
Regards,
Richie

Learning R
4dpiecharts.com

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] What to do when you can't reproduce CRAN R CMD check unit test failures?

[Richard Cotton]

Thanks Bob,

I'd forgotten about the option to run win-builder against R-devel.

Though it seems that in this case, all the tests are passing there too.

http://win-builder.r-project.org/21kc9XGKdANF/examples_and_tests/tests_i386/testthat.Rout
http://win-builder.r-project.org/21kc9XGKdANF/examples_and_tests/tests_x64/testthat.Rout

I'm now completely out of ideas as to where the problem could be.


On 11 May 2016 at 15:46, boB Rudis  wrote:
> did you try winbuilder R-devel? I occasionally (ok, often) forget to
> do that and it sometimes kick out different errors than R-devel on
> local systems.
>
> On Wed, May 11, 2016 at 2:40 AM, Richard Cotton  wrote:
>> Yesterday I uploaded a new version of the pathological package to
>> CRAN.  It was initially accepted but today I got a message saying that
>> some of the tests for the decompose_path function are failing under
>> Windows.
>>
>> I've tested the package on a local Windows 10 machine with R-3.3.0 and
>> R-devel, and in Win 7 and Win 8 compatibility modes, and on Windows
>> Server 2012 via AppVeyor.  In all cases, all the tests pass.
>>
>> I tried the CRAN win builder service today, and again, all tests pass.
>> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_i386/testthat.Rout
>> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_x64/testthat.Rout
>>
>> The failure portion of the output I got from Uwe is as follows:
>>
>> * checking tests ... ERROR
>> Running the tests in 'tests/testthat.R' failed.
>> Last 13 lines of output:
>>   1. Failure: decompose_path handles paths with no directory and a
>> single extension in the filename. (@test_decompose_path.R#42)
>>   2. Failure: decompose_path handles paths with no directory and a
>> double extension in the filename. (@test_decompose_path.R#72)
>>   3. Failure: decompose_path handles paths with no directory and no
>> extension in the filename. (@test_decompose_path.R#103)
>>   4. Failure: decompose_path handles filenames containing a '.' and an
>> extension. (@test_decompose_path.R#133)
>>   5. Failure: decompose_path handles the current directory as '.'.
>> (@test_decompose_path.R#221)
>>   6. Failure: decompose_path handles the parent directory as '..'.
>> (@test_decompose_path.R#236)
>>   7. Failure: decompose_path handles files inside '.'.
>> (@test_decompose_path.R#251)
>>   8. Failure: decompose_path works with a character vector input.
>> (@test_decompose_path.R#321)
>>   9. Failure: decompose_path works with a factor input.
>> (@test_decompose_path.R#333)
>>   1. ...
>>
>>
>> Since this isn't hugely informative as to the problem, I'd like
>> general advice on how I can diagnose a failing test when I can't
>> reproduce it.
>>
>> It would also be useful if anyone can run R CMD check and see if they
>> find test failures.
>>
>> The CRAN release is here (the problematic version is 0.0-8):
>> https://cran.r-project.org/web/packages/pathological
>>
>> and the github version is currently in the same state, available here:
>> https://github.com/richierocks/pathological
>>
>> --
>> Regards,
>> Richie
>>
>> Learning R
>> 4dpiecharts.com
>>
>> __
>> R-package-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-package-devel



-- 
Regards,
Richie

Learning R
4dpiecharts.com

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel