take.
Cheers,
Chris
-Original Message-
From: Martyn Plummer [mailto:plumm...@iarc.fr]
Sent: Wednesday, 24 January 2018 4:20 AM
To: Chris Brien; e...@debian.org; murdoch.dun...@gmail.com
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
On Tue, 2018
-Original Message-
> From: Martyn Plummer [mailto:plumm...@iarc.fr]
> Sent: Tuesday, 23 January 2018 4:26 AM
> To: Chris Brien; e...@debian.org; murdoch.dun...@gmail.com
> Cc: r-package-devel@r-project.org
> Subject: Re: [R-pkg-devel] Licensing of an R package
>
> On
packages.
Cheers,
Chris
-Original Message-
From: Martyn Plummer [mailto:plumm...@iarc.fr]
Sent: Tuesday, 23 January 2018 4:26 AM
To: Chris Brien; e...@debian.org; murdoch.dun...@gmail.com
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
On Fri
t; Cheers,
>
> Chris
>
>
> -Original Message-
> From: Dirk Eddelbuettel [mailto:dirk.eddelbuet...@gmail.com] On
> Behalf Of Dirk Eddelbuettel
> Sent: Saturday, 20 January 2018 2:30 AM
> To: Duncan Murdoch
> Cc: Chris Brien; r-package-devel@r-project.org
>
ehalf Of Dirk
Eddelbuettel
Sent: Saturday, 20 January 2018 2:30 AM
To: Duncan Murdoch
Cc: Chris Brien; r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
Chris,
I am with Duncan here.
You can license _your_ package any way you want and prefer. I like GPL.
You se
On 19 January 2018 at 10:00, Dirk Eddelbuettel wrote:
| Also look eg at our Rblpapi package. The Bloomberg API is not open source,
| but they allow distribution of the (pre-built) library and headers. Our
| package, building on top, is GPL-2+. No issues. (This example is extra fun
Correction.
Chris,
I am with Duncan here.
You can license _your_ package any way you want and prefer. I like GPL.
You seem to imply that the GPL license prohibits linking against commercial
code. If that were the case we'd never have R, Emacs, gcc/g++, ... on
Windows or macOS or any of the now-essentially
On 19/01/2018 3:31 AM, Chris Brien wrote:
Dear list members,
I have come to realize that my understanding of free software licensing was
somewhat naïve. The problem is that I now find that, in spite of spending quite
a bit of time reading about various licenses on the web, I have been unable t
Behalf Of
> Barry Rowlingson
> Sent: Friday, 19 January 2018 8:00 PM
> To: Chris Brien
> Cc: r-package-devel@r-project.org
> Subject: Re: [R-pkg-devel] Licensing of an R package
>
> Chris,
>
> you've not said what *you* would like the license for your software to
> do. You
kage-devel [mailto:r-package-devel-boun...@r-project.org] On Behalf
Of Brian G. Peterson
Sent: 19 January 2018 20:56
To: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
Chris, on C) even commercial packages have licenses. If the commercial package
contains
To: Chris Brien
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
Chris,
you've not said what *you* would like the license for your software to do. You
could release the software under a "public domain", "no rights reserved" style
li
rs,
Chris
From: stefan.mckinnon.edwa...@gmail.com
[mailto:stefan.mckinnon.edwa...@gmail.com] On Behalf Of Stefan McKinnon
Høj-Edwards
Sent: Friday, 19 January 2018 7:58 PM
To: Chris Brien
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Licensing of an R package
Hi Chris,
Just for clarifi
-pkg-devel] Licensing of an R package
Hi Chris,
Just for clarification, there are at least two aspects that affect how you can
license your package.
A) Do you distribute `bar` with your package, or are you simply calling
routines in `bar`?
B) What is the exact license of `bar`?
C) Is there a
Chris,
you've not said what *you* would like the license for your software to do.
You could release the software under a "public domain", "no rights
reserved" style license, and then if people want to link it with
proprietary materials then nothing can stop them. But it wouldn't stop
people comme
Hi Chris,
Just for clarification, there are at least two aspects that affect how you
can license your package.
A) Do you distribute `bar` with your package, or are you simply calling
routines in `bar`?
B) What is the exact license of `bar`?
C) Is there a reason for this secrecy of `bar`? If we kne
Dear list members,
I have come to realize that my understanding of free software licensing was
somewhat naïve. The problem is that I now find that, in spite of spending quite
a bit of time reading about various licenses on the web, I have been unable to
identify a suitable license for the situa
16 matches
Mail list logo
