Ports with many licenses
Kurt Jaeger
pi at freebsd.org
Tue Nov 6 08:15:37 UTC 2018
Hi!
> I am working on creating and adopting some ports and I see that a
> it is very frequent that distfiles have multiple licenses with the following
> scheme: the project has one main license (declared in a COPYING or
> LICENSE file for example) but also many files with their own licenses
> (a frequent case is with files related to the GNU tools, for examples
> Makefile.in).
>
> Then I wondered what should I really write in the LICENSE field: should I
> take care only of the main license or should I track all licenses of all files?
For a first cut, just take care of the main license. If you find time
after doing all the other work to update/create a port, then you
can still track all the licenses.
> This second case looks very impractical: it would often (always?) require
> to inspect all files one by one.
Yes. Therefore, do it only if you find nothing else to do 8-}
--
pi at opsec.eu +49 171 3101372 2 years to go !
More information about the freebsd-ports
mailing list