Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Apr 2017 13:24:00 +0200
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        "Carlos J. Puga Medina" <cpm@FreeBSD.org>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/LRapw2rJrlR8n1itNC03sNg
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

"Carlos J. Puga Medina" <cpm@FreeBSD.org> 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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170430130851.79ad376f>