[Rd] Non-GPL C (or R) inside of a package

From: Jeffrey Ryan <jeffrey.ryan_at_lemnica.com>
Date: Tue, 30 Aug 2011 12:50:37 -0500


I am interested in creating a package that requires non-GPL'd (commercial) C code to work. In essence it is a single .c file with no use of R headers (all .C callable functions). For example's sake:

  1 #include <stdio.h>
  3 void test (int *a) {
  4 *a = 101;
  5 }

The package isn't destined for CRAN, and I realize that this isn't R-legal, but looking for some expert advice from anyone else who may have encountered this previously.

The question is whether or not one can distribute code that has multiple licenses (.c or individual .R files), including some that are not GPL-compatible, as a tar.gz (or binary) file. i.e., does the packaging process [R CMD ***] cause everything to become GPL, as we are using R itself to build the package?

I can of course provide the C libs in this case as a separate install, but that adds complexity to the overall build and install process.


Jeffrey Ryan


	[[alternative HTML version deleted]]

R-devel_at_r-project.org mailing list
Received on Tue 30 Aug 2011 - 17:52:55 GMT

This quarter's messages: by month, or sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

All messages

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Wed 31 Aug 2011 - 15:50:28 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.

list of date sections of archive