From owner-svn-ports-all@freebsd.org Sun Apr 30 11:24:07 2017 Return-Path: Delivered-To: svn-ports-all@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 72462D57B2B for ; Sun, 30 Apr 2017 11:24:07 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay07.ispgateway.de (smtprelay07.ispgateway.de [134.119.228.103]) (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 3C2C2125; Sun, 30 Apr 2017 11:24:06 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.164.112] (helo=fabiankeil.de) by smtprelay07.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1d4mxJ-0006V0-6G; Sun, 30 Apr 2017 13:23:57 +0200 Date: Sun, 30 Apr 2017 13:24:00 +0200 From: Fabian Keil To: "Carlos J. Puga Medina" Cc: svn-ports-all@freebsd.org Subject: Re: svn commit: r439777 - in head/www: . iridium iridium/files Message-ID: <20170430130851.79ad376f@fabiankeil.de> In-Reply-To: <201704292300.v3TN0Xi5007533@repo.freebsd.org> References: <201704292300.v3TN0Xi5007533@repo.freebsd.org> Reply-To: svn-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/LRapw2rJrlR8n1itNC03sNg"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2017 11:24:07 -0000 --Sig_/LRapw2rJrlR8n1itNC03sNg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Carlos J. Puga Medina" wrote: > Author: cpm > Date: Sat Apr 29 23:00:33 2017 > New Revision: 439777 > URL: https://svnweb.freebsd.org/changeset/ports/439777 >=20 > Log: > Add new port www/iridium Thanks. > Iridium is a free, open, and libre browser modification of the Chromium > code base, with privacy being enhanced in several key areas. > =20 > Automatic transmission of partial queries, keywords, metrics to central > services is inhibited and only occurs with consent. > =20 > WWW: https://iridiumbrowser.de/ >=20 > Added: [...] > Modified: head/www/iridium/Makefile This inherits the "FreeBSD Chromium Api Key" from www/chromium and enables it by default. This seems like a significant deviation from the upstream to me and worth explaining in the pkg-descr. See also: https://iridiumbrowser.de/faq.html#why-synching-and-signing-in-to-iridium-o= r-google-does-not-work The default of enabling "proprietary_codecs=3Dtrue" doesn't seem to match the pkg-descr content either. Does setting this actually have an effect when using the Iridium distfile? Wouldn't the patent issues (assuming they exist) warrant a RESTRICTED flag? Using the same CPE_* flags as www/chromium seems strange to me as well but they don't seem to be sufficiently documented to decide whether or not that's correct. The MASTER_SITES resource seems to support https. Fabian --Sig_/LRapw2rJrlR8n1itNC03sNg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWQXJUAAKCRAFiohV/3dU nS1VAKCd9JaSKylfgt660p+oBB6ak2hB5QCfQHsoPnOrKtm5R5N9SvuyU5+bKE4= =oS09 -----END PGP SIGNATURE----- --Sig_/LRapw2rJrlR8n1itNC03sNg--