Bug 216435 - [new port] www/iridium: Iridium Secure Browser
Summary: [new port] www/iridium: Iridium Secure Browser
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL: https://iridiumbrowser.de/
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-24 14:06 UTC by Slawomir Wojciech Wojtczak
Modified: 2017-05-02 21:43 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Slawomir Wojciech Wojtczak 2017-01-24 14:06:30 UTC
All in topic.
Comment 1 Alexandre C. Guimarães freebsd_committer freebsd_triage 2017-03-13 22:52:10 UTC
There is a Port already, available on github:

https://github.com/cpu82/iridium
Comment 2 Chris Hutchinson 2017-03-13 23:04:10 UTC
(In reply to Le Baron d'Merde from comment #1)
> There is a Port already, available on github:
> 
> https://github.com/cpu82/iridium

Looks great!
I see the maintainer is chromium
If that's a valid user/group, why is it not
in the ports tree already?

I'm going to fork it, and give it a spin.
Hope it works! :-)

Thanks for the clue, Le Baron d'Merde!

--Chris
Comment 3 Slawomir Wojciech Wojtczak 2017-03-14 07:51:33 UTC
(In reply to Le Baron d'Merde from comment #1)
Why not directly in Ports?
Comment 4 Chris Hutchinson 2017-03-14 19:53:42 UTC
well I forked a copy from github.
Examined it more closely, then packed up the necessary
bits, and dumped them into ports/www (as iridium).
Then simply issued a make. Followed by a make install.
It builds just fine -- albeit a bit slowly, as blowzilla
does. Another point to make; the src download (iridium)
is around half a gigabyte (compressed). So you won't be
building this on anything light on resources.

I can confirm it's ready to hit the ports tree. I
have a typescript ( script(1) ) of the entire build/
install process, to prove it! :-)

I'd create a pr(1) for the port' addition. But I didn't
create the port, cpm@ did. So I guess the best route is
to wait till Carlos submits it -- or prod Carlos to do it. ;-)

My evaluation;
It works every bit the same as the chromium port does.
But it has more settings/options related to secutity.
I found it a bit "klunky", not unlike I found the
chromium port. It (like chromium) isn't very good
with modern web standards -- fancy css3, and such.
OTOH iridium is built from an older version of
chromium (54.0). From around mid 2016, I think.
So I might retrieve a copy of head, and see how
that builds/works.

Well. There you have it. :-)

--Chris
Comment 5 Slawomir Wojciech Wojtczak 2017-03-16 10:07:15 UTC
Thank You ;)
Comment 6 Carlos J. Puga Medina freebsd_committer freebsd_triage 2017-03-23 10:14:57 UTC
I haven't committed iridium into the ports tree because some CVE security vulnerabilities may impact on this version. Note that the iridium browser is based on chromium source and the latest version released is a bit old.

http://lists.inai.de/pipermail/iridium/2017-March/000630.html

I guess that iridium developers will update iridium to a more recent version.
Comment 7 Carlos J. Puga Medina freebsd_committer freebsd_triage 2017-05-02 21:43:52 UTC
iridium browser was added to the ports collection.

https://svnweb.freebsd.org/ports?view=revision&revision=439777