Hello everyone,
I hope this email finds you well.
I?m sorry to bother you, it?s the very first time I?m submitting a package to CRAN.
Recently my submission got rejected with the following feedback:
Non-FOSS package license (file LICENSE)
Suggests or Enhances not in mainstream repositories:
velocyto.R
Found the following (possibly) invalid URLs:
URL: https://cran.r-project.org/web/packages/Seurat/index.html
From: inst/doc/a_SuperCell.html
Status: 200
Message: OK
CRAN URL not in canonical form
The canonical URL of the CRAN page for a package is
https://CRAN.R-project.org/package=pkgname<https://cran.r-project.org/package=pkgname>
Size of tarball: 9076436 bytes
Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64
Check: package dependencies, Result: NOTE
Package suggested but not available for checking: ?velocyto.R'
The license we?re using is the standard CC BY-NC-ND 4.0 and is listed among the accepted licenses for CRAN.
I fixed the URL issue but how can I make CRAN accept the package ?
Thank you advance for your time and your help !
Have a nice day.
Best Regards,
Matei Teleman
[R-pkg-devel] Help for understanding CRAN rejection
2 messages · Matei Teleman, Ivan Krylov
? Mon, 8 Jul 2024 15:12:24 +0000 Matei Teleman <matei.teleman at unil.ch> ?????:
Non-FOSS package license (file LICENSE)
The license we?re using is the standard CC BY-NC-ND 4.0 and is listed among the accepted licenses for CRAN
Instead of putting the license text in a file inside the package (that would have to match byte by byte in order to be recognised automatically, or may be subtly different from the original with potentially drastic legal consequences), use the name of the license listed at [1]: License: CC BY-NC-ND 4.0 If you want to keep the full text of the license in your source code repository, put it in a file that you exclude from the source package using .Rbuildignore. I'm assuming you've already seen the CC FAQ [2] that recommends against using CC licenses for software and chose it because it offers restrictions for commercial use and distribution of derivatives. Too bad none of the other licenses at [1] offer the same kind of restrictions.
Suggests or Enhances not in mainstream repositories:
velocyto.R
Just making sure: have you provided the instructions for obtaining velocyto.R in the 'Description' field of the DESCRIPTION file?