Date: Tue, 14 Mar 2017 19:53:42 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216435] [new port] www/iridium: Would Be Great to Have on FreeBSD - https://iridiumbrowser.de/ Message-ID: <bug-216435-13-RfqkIJDVy6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216435-13@https.bugs.freebsd.org/bugzilla/> References: <bug-216435-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216435 --- Comment #4 from Chris Hutchinson <portmaster@bsdforge.com> --- 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 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216435-13-RfqkIJDVy6>