Skip to content

Licence for datasets in a R-package

7 messages · Duncan Murdoch, Gábor Csárdi, Gabor Grothendieck +2 more

#
On 21/07/2014 12:17 PM, Gionata Bocci wrote:
If you are not distributing the package to anyone else, you can ignore 
the warning about the bad license field.

If you plan to distribute it on a public repository, you should ask the 
policies of the repository to find out what to do about this. CRAN 
policies are listed at 
http://cran.r-project.org/web/packages/policies.html.  There's a link 
from there to the list of acceptable licenses, and it includes some CC 
licenses.

If some parts of the package are licensed one way and others are 
licensed in another way, you'll probably need a COPYRIGHTS file to 
describe it.

Other repositories (e.g. Bioconductor, Github) presumably have their own 
policies on this, but I don't know where to find those.

Duncan Murdoch
#
On Mon, Jul 21, 2014 at 12:49 PM, Duncan Murdoch
<murdoch.duncan at gmail.com> wrote:
[...]
In practice, CRAN maintainers do not allow multiple licenses for parts
of the same package. At least they did not for my package a couple of
months ago.
At Github, they do not care, you can do whatever you want (as long as
it is legal, I guess).

Gabor

[...]
#
On Mon, Jul 21, 2014 at 12:54 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote:
If that is the case then you could put your data files in a separate
package from the code with one depending on the other.
#
On Mon, Jul 21, 2014 at 1:56 PM, Gabor Grothendieck
<ggrothendieck at gmail.com> wrote:
Yes, and sometimes this even makes sense, as the data does not change often.

This was, however, a package with several data sets, accompanying a
book. So this would have been quite cumbersome.

Gabor