On Wed, 2015-06-03 at 09:51 +0200, Uwe Ligges wrote:
On 03.06.2015 09:48, Berry Boessenkool wrote:
Hi,
after submitting my package update, CRAN (Brian Ripley) found a couple of
warnings / messages.
URLs that are not longer existent, a non-ASCII character from copypasting,
On Mon, 2015-07-20 at 07:36 +0200, Antonio José Saez Castillo wrote:
When checking a package I am getting
* checking package dependencies ... NOTE
No repository set, so cyclic dependency check skipped
This is an old source of discussion and I've found a lot of suggestions,
but none of
On Thu, 2016-03-03 at 16:42 +0100, Uwe Ligges wrote:
>
> On 03.03.2016 16:08, Martyn Plummer wrote:
> > On Thu, 2016-03-03 at 15:45 +0100, Sebastien Moretti wrote:
> > > I have just found that R 2 filled by itself the NAMESPACE file
> > > with
> > >
On Thu, 2016-03-03 at 15:45 +0100, Sebastien Moretti wrote:
> I have just found that R 2 filled by itself the NAMESPACE file with
> # Export all names
> exportPattern(".")
>
> # Import all packages listed as Imports or Depends
> import(
> cluster
> )
>
>
> So I filled the NAMESPACE file with
On Thu, 2016-05-12 at 01:09 -0500, Kevin Ushey wrote:
> Is it possible that `getwd()` is reporting something on the CRAN
> build
> servers that your `decompose_path()` doesn't handle? For example,
> your
> tests fail for me if I run them while in the root directory (on OS
> X).
It does not work
Short answer: use the R macro ISNAN instead. See the Writing R
Extensions manual for details.
Long answer: The default standard for C++ code in R packages is C++98,
which does not define a function "isnan". The C++11 standard introduced
a std::isnan function to C++. What you were previously
Most people who want to interface to an external library embed the source code
of the library in their R package. I see that ginac is a C++ library which
creates additional problems. Only a few R packages interface to an external
C++ library (e.g. the interfaces to SYMPHONY, gdal, QuantLib,
On Wed, 2017-09-20 at 09:45 -0500, Dirk Eddelbuettel wrote:
> Thierry,
>
> This has always been a considerable puzzle, and the source of some amusement,
> to me. It is a clear design bug in Rscript because _code that would
> otherwise work_ will not if it happens to rely on library(methods). S4
On Wed, 2017-10-25 at 10:52 +0200, Uwe Ligges wrote:
>
> On 25.10.2017 10:48, "Jens Oehlschlägel" wrote:
> > Good morning,
> >
> > Duncan has announced that he steps back from the maintenance of Rtools.
> > Where will I find the new Rtools toolchain that complements Microsofts
> > R-version?
>
On Wed, 2018-02-07 at 15:17 +0300, Alexander Loboda wrote:
> Dear all,
>
> I'm trying to build a package that uses c++11 code and sub-directories
> in src/ according to the "Writing R Extensions" manual, but it seems
> like R CMD doesn't want to compile the code with c++11 flags when source
>
On Fri, 2018-01-19 at 20:28 +, Chris Brien wrote:
> Hi Dirk & Duncan,
>
> I too like GPL and I had thought that the situation was as Duncan
> outlines. Consequently, I had licensed `foo' as GPL >= 2.
>
> However, because I have been unable to find a discussion of my case,
> in spite of the
that CRAN is legally entitled to distribute Windows and MacOS
binaries. In any case, the vast majority of CRAN packages are not
problematic as they are licenced under GPL or a GPL-compatible license
without linkage to a non-free library.
Martyn
> Cheers,
>
> Chris
>
>
>
I agree with Brian. This type of license is classified by the Free
Software Foundation as "lax" or "permissive" because it does not
prevent incorporation of the code into proprietary software.
Here is what Richard Stallman has to say: https://www.gnu.org/licenses/
license-compatibility.en.html
On Thu, 2018-03-01 at 16:05 +, David Stanley wrote:
> Hi Everyone,
>
> I’m new to this list but hopefully you can help me.
>
> I’m working on updating my apaTables package (most recent code: https
> ://github.com/dstanley4/apaTables)
>
> However, I’m encountering problems passing the CRAN
14 matches
Mail list logo
