svn commit: r439777 - in head/www: . iridium iridium/files

[Fabian Keil]

"Carlos J. Puga Medina" <cpm at FreeBSD.org> wrote:

> Author: cpm
> Date: Sat Apr 29 23:00:33 2017
> New Revision: 439777
> URL: https://svnweb.freebsd.org/changeset/ports/439777
> 
> 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.
>   
>   Automatic transmission of partial queries, keywords, metrics to central
>   services is inhibited and only occurs with consent.
>   
>   WWW: https://iridiumbrowser.de/
> 
> 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-or-google-does-not-work

The default of enabling "proprietary_codecs=true" 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20170430/89cf3a49/attachment.sig>