Skip to content

Commit 674124c

Browse files
committed
added a 'what license can I use' FAQ entry
1 parent ff85fe3 commit 674124c

File tree

2 files changed

+32
-0
lines changed

2 files changed

+32
-0
lines changed

ChangeLog

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
2014-08-18 Dirk Eddelbuettel <[email protected]>
2+
3+
* vignettes/Rcpp-FAQ.Rnw: Added a new entry regarding licensing of
4+
packages stressing that any combined work linking to the GPL-ed R will
5+
also be under the terms of the GNU General Public License.
6+
17
2014-08-06 Christian Authmann <[email protected]>
28

39
* inst/include/Rcpp/InternalFunctionWithStdFunction.h: Extend the

vignettes/Rcpp-FAQ.Rnw

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,6 +162,32 @@ Additional packages that we have found useful are
162162
a package but it too is entirely optional.
163163
\end{description}
164164

165+
\subsection{What licenses can I choose for my code?}
166+
167+
The \pkg{Rcpp} package is licensed under the terms of the
168+
\href{http://www.gnu.org/licenses/gpl-2.0.html}{GNU GPL 2 or later}, just like
169+
\proglang{R} itself. A key goal of the \pkg{Rcpp} package is to make
170+
extending \proglang{R} more seamless. But by \textsl{linking} your code against
171+
\proglang{R} (as well as \pkg{Rcpp}), the combination is bound by the GPL as
172+
well. This is very clearly
173+
stated at the
174+
\href{https://www.gnu.org/licenses/gpl-faq.html#GPLStaticVsDynamic}{FSF website}:
175+
176+
\begin{quote}
177+
Linking a GPL covered work statically or dynamically with other modules is
178+
making a combined work based on the GPL covered work. Thus, the terms and
179+
conditions of the GNU General Public License cover the whole combination.
180+
\end{quote}
181+
182+
So you are free to license your work under whichever terms you find suitable
183+
(provided they are GPL-compatible, see the
184+
\href{http://www.gnu.org/licenses/licenses.html}{FSF site for details}). However,
185+
the combined work will remain under the terms and conditions of the GNU General
186+
Public License. This restriction comes from both \proglang{R} which is GPL-licensed
187+
as well as from \pkg{Rcpp} and whichever other GPL-licensed components you may
188+
be linking against.
189+
190+
165191
\section{Compiling and Linking}
166192

167193
\subsection{How do I use \pkg{Rcpp} in my package ?}

0 commit comments

Comments
 (0)