From owner-freebsd-ports@FreeBSD.ORG Wed May 19 23:51:41 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC5B1065672 for ; Wed, 19 May 2010 23:51:41 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 69B028FC19 for ; Wed, 19 May 2010 23:51:39 +0000 (UTC) Received: by pvg3 with SMTP id 3so288268pvg.13 for ; Wed, 19 May 2010 16:51:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=btLQgdbNzTR/KkhqrrcKxEtM0xW3uj55PX2bRpIXs3k=; b=iaJyc4v3SZbberRr9jLIE0/vJ1N0TcOo0CpwmAgG9IY0w+M7jxVYkUarytUNAoBK3i CntYbhTV5nUAhhkYNELJHaT7NKbA/BJzeJm6C7xBBkQM/6PytSGNQD8ONszfpfesGX18 W3Tk+fFEyg3wgOG1FIeB7ocViZ8QX3pgYBFuM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=KUKvW0Y5z21xvQEvkjg7+hK1DuGpmSMdar6wXibIKu22fT0k/Z5bmzzv1268Uxle6X pbmERLV4WxTvjNwtDIMTUawohPPUo0ViupYdJ/ayE28xSkGjiB8+/cH+i6Aw94w143VY TpRlEW7vck8yQNYSYZQUZPaiuD/QPPMzlC0l4= Received: by 10.143.85.4 with SMTP id n4mr6246847wfl.312.1274313095388; Wed, 19 May 2010 16:51:35 -0700 (PDT) Received: from dhcp-173-37-1-134.cisco.com (nat.ironport.com [63.251.108.100]) by mx.google.com with ESMTPS id 21sm6377333pzk.12.2010.05.19.16.51.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 May 2010 16:51:33 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: <20100519185406.GA67403@comcast.net> Date: Wed, 19 May 2010 16:51:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <07FC36C8-5B95-4DCA-967A-8FAF4D062D3F@gmail.com> References: <20100518224102.GH326@comcast.net> <4BF3D549.90305@dataix.net> <20100519185406.GA67403@comcast.net> To: Charlie Kester X-Mailer: Apple Mail (2.1078) Cc: freebsd-ports@freebsd.org Subject: Re: GPLv3-licensed ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 23:51:41 -0000 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=