Dear Marc
> 2. Can non-GPL compatible packages for R even be created (even if "pure R"),
> based upon the interpretation of the GPL that Christian has postulated?
I am not trying to offer my own interpretation of the GPL, which is entirely
irrelevant. (If anyone is interested, I fall on the "pr
Dear Simon
Thank you for the link. This is exactly the kind of statement that I was
looking for.
I searched the archives for any mention of the GPL, for posts by Prof. Leisch
and some other keywords before posting to the list. Could this statement be
added to the R FAQ and/or the CRAN reposito
>
>
>
> 1. If I develop and distribute an R package which depends on another package
> that is released under the GPL, I have to release my package in a
> GPL-compatible way.
It is probably worth remembering that declaring a 'dependency' of package foo
on package bar in the R inter-package s
On Jan 25, 2013, at 2:45 PM, Simon Urbanek wrote:
>
> On Jan 25, 2013, at 3:32 PM, Marc Schwartz wrote:
>
>>
>> On Jan 25, 2013, at 12:16 PM, Christian Sigg wrote:
>>
>>> Dear Duncan
>>>
I don't think my point contradicts the FSF interpretation. I think they
were talking about
On Jan 25, 2013, at 3:32 PM, Marc Schwartz wrote:
>
> On Jan 25, 2013, at 12:16 PM, Christian Sigg wrote:
>
>> Dear Duncan
>>
>>> I don't think my point contradicts the FSF interpretation. I think they
>>> were talking about using GPL modules in a program you distribute, with the
>>> impli
On Jan 25, 2013, at 12:16 PM, Christian Sigg wrote:
> Dear Duncan
>
>> I don't think my point contradicts the FSF interpretation. I think they
>> were talking about using GPL modules in a program you distribute, with the
>> implication that you are distributing the modules along with your pr
On 25/01/2013 1:16 PM, Christian Sigg wrote:
Dear Duncan
> I don't think my point contradicts the FSF interpretation. I think they were
talking about using GPL modules in a program you distribute, with the implication
that you are distributing the modules along with your program. However, I
> I am aware of those discussions, and am not advocating for a change of the
> current practices of the CRAN maintainers. But if the current practices of
> the R project are in conflict with the FSF interpretation of the GPL, they
> need to be addressed.
Let me correct my last sentence to "...,
Dear Marc
The GPL FAQ section that I quoted addresses all the points that you raise:
> There are some questions that need to be answered, since these types of
> questions have to be answered within specific contexts. For example:
>
> 1. Is your package "pure R" code and contains only code that
Dear Duncan
> I don't think my point contradicts the FSF interpretation. I think they were
> talking about using GPL modules in a program you distribute, with the
> implication that you are distributing the modules along with your program.
> However, I could be wrong. If I am wrong and the F
Christian,
In my mind, rightly or wrongly, it boils down to these four points :
1. CRAN policy excludes closed source packages; i.e., every single
package on CRAN includes its C code, if any. If an R package included a
.dll or .so which linked at C level to R, and that was being distributed
On Jan 25, 2013, at 6:32 AM, Duncan Murdoch wrote:
> On 13-01-24 12:22 PM, Christian Sigg wrote:
>> I intend to submit a newly developed package to CRAN (to be licensed under
>> the GPL), which prompted me to re-read the GPL FAQ. The following section
>> caught my attention:
>>
>>> If a progr
I agree, environment modules really come into their own when you need to switch
back and forth between different versions, as I do when testing my packages.
Since environment modules are used on the cluster I work on, it's actually
easier for me to use them on my local machines than to change w
On 13-01-24 12:22 PM, Christian Sigg wrote:
I intend to submit a newly developed package to CRAN (to be licensed under the
GPL), which prompted me to re-read the GPL FAQ. The following section caught my
attention:
If a programming language interpreter is released under the GPL, does that mean
The R-exts manual still says
Note also that for running @LaTeX{}, the Debian @acronym{GNU}/Linux
@acronym{CRAN} check systems use the Debian TeXLive@footnote{currently
the long obsolete TeXLive 2009.} distribution
(@uref{http://packages.debian.org/@/en/@/sid/@/texlive}); the Fedora and
a
I built a patch (
https://github.com/3jb/R_layers/blob/master/add_pdf_layers_r61733.diff)
for grDevice/devPS.c adding an argument 'onepage' to pdf(), if set to
TRUE, successive plots will be printed to layers within a single pdf
document page rather than successive documents, or successive pages wi
I intend to submit a newly developed package to CRAN (to be licensed under the
GPL), which prompted me to re-read the GPL FAQ. The following section caught my
attention:
> If a programming language interpreter is released under the GPL, does that
> mean programs written to be interpreted by it
17 matches
Mail list logo
