Date: Tue, 6 Nov 2018 09:15:34 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Lorenzo Salvadore <phascolarctos@protonmail.ch> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Ports with many licenses Message-ID: <20181106081534.GB1940@home.opsec.eu> In-Reply-To: <z09FWhtGq-Ke-fA8rAoVLJjpSVoH_pwJEW-CX7qTGE7Rmm4b6VxYVa46uWMaXLxulWjztuSPl57DjP2899SIAzkp6IP-e8n-I6A81Tki0iY=@protonmail.ch> References: <z09FWhtGq-Ke-fA8rAoVLJjpSVoH_pwJEW-CX7qTGE7Rmm4b6VxYVa46uWMaXLxulWjztuSPl57DjP2899SIAzkp6IP-e8n-I6A81Tki0iY=@protonmail.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
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@opsec.eu +49 171 3101372 2 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181106081534.GB1940>