Hi all. I know nothing about software licenses. Some recent discussion on the Rstan/Stanheaders merger thread suggests that packages that depend on GPL-licensed packages might need to be published under GPL licenses.
Is there some important and well-known subtlety that makes the rstan/stanheaders issue on the thread linked above clearly thornier than the thousands of non-GPL R packages with GPL dependencies? For example, is the concern restricted to packages that use rstan to pre-compile a bunch of c++ when they’re installed? Brief googling suggests that maybe there is no such subtlety; i.e. that perhaps any package that depends on a GPL package needs to be distributed under GPL. Note that multiple R packages in stan-dev are not compliant with this interpretation.
It might be important/useful to provide some clearer community guidance for licensing rstan reverse-dependencies. For example, the Step by step guide for creating a package that depends on RStan doesn’t mention this issue at all. rstantools::rstan_create_package() adds a GPL-3 by default, but with the option to not add the license and no indication that adding the license might be legally required if the intention is to release/distribute the package.