Date: Wed, 19 May 2010 16:51:30 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Charlie Kester <corky1951@comcast.net> Cc: freebsd-ports@freebsd.org Subject: Re: GPLv3-licensed ports Message-ID: <07FC36C8-5B95-4DCA-967A-8FAF4D062D3F@gmail.com> In-Reply-To: <20100519185406.GA67403@comcast.net> References: <20100518224102.GH326@comcast.net> <4BF3D549.90305@dataix.net> <20100519185406.GA67403@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 19, 2010, at 11:54 AM, Charlie Kester wrote: > On Wed 19 May 2010 at 05:10:49 PDT jhell wrote: >> Adding to this bundle of madness... >>=20 >> I believe that it would be best practice to keep ports/LEGAL = up-to-date >> with this list. >>=20 >> Those who already have ports on a machine may find it more usefull to >> find them there. >>=20 >> Quoting ports/LEGAL: >> "Some of the ports in this directory have restrictive copyrights" and >> GPLv3 I believe certainly would fall under that category. >=20 > Yes, I don't what the original legal concerns were that led to the = wiki > page, but I know that many FreeBSD users are wary of GPLv3. So it = makes > sense to let them know which ports are licensed that way. >=20 > After checking the COPYING files, some more of my ports for the list: >=20 > devel/gengetopt > devel/libYGP > sysutils/iextract > sysutils/gaffitter >=20 > The ports in the devel category are especially noteworthy, since (if I = understand correctly) their license will infect anything > built with them. >=20 > Is ports/LEGAL prominent enough? Should I also add something to the = pkg-descr? As an end-user I don't care about GPLv3 other than from a = philosophical stance; but using GPLv3 with FreeBSD as an employee is a = non-starter, so that's a good primary reason for the wiki page I think. This data should really be inside the Makefile or something = similar to CATEGORIES, etc like Gentoo Linux does (at least you know = what you're getting before you install a package or port). That way = other non-permissive licenses could be audited before the package is = installed and someone could make a decision as to whether or not they = can install it either because of licensing constraints, export issues, = or the like... Thanks, -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07FC36C8-5B95-4DCA-967A-8FAF4D062D3F>