From owner-freebsd-ports@freebsd.org Wed Nov 18 11:01:56 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1503FA32EC6 for ; Wed, 18 Nov 2015 11:01:56 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDAC71788 for ; Wed, 18 Nov 2015 11:01:55 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.184.10] (helo=fabiankeil.de) by smtprelay03.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Zz0Gu-0005ko-GY; Wed, 18 Nov 2015 11:47:28 +0100 Date: Wed, 18 Nov 2015 11:48:39 +0100 From: Fabian Keil To: Roger Marquis Cc: freebsd-ports@freebsd.org Subject: Re: License info Q Message-ID: <20151118114839.431a3adf@fabiankeil.de> Reply-To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/Cwv54pxi0qWgc1r7peR3K/w"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 11:01:56 -0000 --Sig_/Cwv54pxi0qWgc1r7peR3K/w Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Roger Marquis wrote: > I need to get license info from a batch of ports and packages. >=20 > Problem is not all the specified ports/pkgs are installed or have license > info in their Makefile. Is there a reliable way to enumerate port or > package license strings, preferably without fetching a package tarfile? No. Also note that the "license information" in the Makefiles is often misleading[1] and thus not particular useful if you actually care about license compliance. Unfortunately reporting incorrect license information seems to be a waste of time so things are unlikely to improve any time soon: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195807 Fabian [1] The lack of documentation doesn't help. --Sig_/Cwv54pxi0qWgc1r7peR3K/w Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZMV4oACgkQBYqIVf93VJ2qLgCeP2tDHh4WY5YlUILyh9XygfuQ MN8An3D1gP4CKcaaGy9OnzX0ZGQjbake =yLCM -----END PGP SIGNATURE----- --Sig_/Cwv54pxi0qWgc1r7peR3K/w--