Yes. Check out
https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
and also note that CC-BY is not recommended as a software license (by CC
themselves). As there is one-way compatibility, it should be possible to
clarify the situation by putting your derivative work under
Thank you Peter for your response,
It looks ok for the license. The journal's content appears to be under
this license:
https://creativecommons.org/licenses/by/3.0/
Raphael
Le 18/09/2019 à 14:11, peter dalgaard a écrit :
Not a lawyer, but...
I would expect that it depends on what license
Not a lawyer, but...
I would expect that it depends on what license it was published under
originally. If it doesn't explicitly allow the creation of derivative works,
then I would be wary.
-pd
> On 18 Sep 2019, at 13:59 , Raphael Bonnet
> wrote:
>
> Hi everyone,
>
> I just rewrote a bit
Hi everyone,
I just rewrote a bit of Matlab code into R and that I would like to make
it available for the community.
Unfortunately this bit of code has been published by authors that I've
never contacted.
I was wondering if I could submit a package to CRAN by keeping the same
license as
I don't know about Windows 10 but I think that the pointers to Rtools need to
be to the bin subdirectory. Also, it is prudent to have these at the beginning
of the search path, e.g.
PATH=c:\Rtools\bin;c:\Rtools\mingw_64\bin;c:\ProgramF\R\R-3.6.0patched\bin;
I am not sure if the entry for
Hello,
I' have just tried to submit a package to CRAN which has a Bioconductor
dependency. I import "GeneticsPed" in my package but
when installing it, have this error:
ERROR: dependency 'GeneticsPed' is not available for package 'LRQMM'
* removing 'C:/Users/.../LRQMM'.
or this check:
Hello:
"R CMD build bssm" complains:
unable to run 'make clean' in 'src'
This is on a Windows 10 computer with R 3.6.1 installed with, I
think, Rtools35.exe. "sessionInfo()" says, "Platform:
x86_64-w64-mingw32/x64 (64-bit)".
This is trying to build a
