On Wed, Aug 16, 2023 at 11:41 AM Vincent Goulet wrote:
>
> Although late to the party, I thought I might chime in with a different take
> on the question.
>
> Most answers seem to pertain to the actual license used for the package. For
> my part, I read the question as: "GitHub wants me to have
Although late to the party, I thought I might chime in with a different take on
the question.
Most answers seem to pertain to the actual license used for the package. For my
part, I read the question as: "GitHub wants me to have a LICENSE file at the
root of the repository, but R CMD check
If you're using one of the licenses supported by usethis
(https://usethis.r-lib.org/reference/licenses.html), you can just call
the appropriate function and it will do all the setup required to be
both CRAN and GitHub compatible.
Hadley
On Wed, Aug 9, 2023 at 10:10 AM Emanuele Cordano
wrote:
>
In case you're thinking of putting the package on CRAN, note also from
the CRAN policy https://cran.r-project.org/web/packages/policies.html:
> Packages with licenses not listed at
https://svn.r-project.org/R/trunk/share/licenses/license.db will
generally not be accepted.
On 2023-08-09
On Wed, 9 Aug 2023 17:06:01 +0200
Emanuele Cordano wrote:
> I have an R package on Github with a a LICENSE file compliant to
> Github and containing the text of the licence citing in the
> DESCRIPION file. But when I check the package , I obatained the
> following output:
>
> * checking
You have two choices:
* put LICENSE in your .Rbuildignore file so that it shows up on Github
but is excluded from the package
* follow the instructions in
https://cran.r-project.org/doc/manuals/R-exts.html#Licensing to refer to
LICENSE in your DESCRIPTION file. However, CRAN generally
Dear list,
is there a way to put the LICENSE file within an R package like in Github,
I have an R package on Github with a a LICENSE file compliant to Github and
containing the text of the licence citing in the DESCRIPION file. But when
I check the package , I obatained the following output:
*
