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 (suggestion
ly 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
>> | packa
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 t
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
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 functi
