• https://downloads.iridiumbrowser.de/source/ (Download)
• http://nerd.hu/distfiles/ (Download)

• component
• debug

• (2021-07-06) Updated to version: iridium-2021.06.91
• (2021-04-01) Updated to version: iridium-2021.03.88
• (2020-11-05) Updated to version: iridium-2020.11.85
• (2020-04-12) Updated to version: iridium-2020.04.81
• (2020-04-02) Updated to version: iridium-2020.03.80
• (2019-11-10) Updated to version: iridium-2019.11.78
• (2019-04-17) Updated to version: iridium-2019.04.73
• (2018-11-21) Updated to version: iridium-2018.11.71
• (2018-11-06) Updated to version: iridium-2018.11.70
• (2018-06-06) Updated to version: iridium-2018.5.67

Log message:
sync arm64 ffmpeg config

Log message:
mark BROKEN-i386, build fails due to sse2 problem with simd zlib code

Log message:
update to 2021.06.91

Log message:
remove ports libexecinfo, we now have a libunwind-based libexecinfo in base

Log message:
chromium, iridium: removes RTLD_NODELETE removal patches
ok robert@

Log message:
Bump the REVISION on all ports that use the python2 version of
py-setuptools.
Also change the lang/python module to use the new
devel/py2-setuptools for python2 ports
ok sthen@

Log message:
mark these as broken on powerpc64. while there, fix the COMMENT for electron.
ok robert@

Log message:
update to 2021.03.88

Log message:
remove carriage returns ('\r') from patch files and set FIX_CRLF_FILES

Log message:
Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.

Log message:
put back BROKEN-i386 in chromium and add it to iridium, the binaries
cannot be loaded, they immediately exit:
: sthen@i386.p; chrome
/usr/local/bin/chrome[60]: /usr/local/chrome/chrome: Cannot allocate memory
: sthen@i386.p; size /usr/local/chrome/chrome
text	data	bss	dec	hex
180104608	3805736	1949616	185859960	b13ff78
exiting happens very early, before ld.so loads libraries:
: sthen@i386.p; LD_DEBUG=1 /usr/local/chrome/chrome
ksh: /usr/local/chrome/chrome: Cannot allocate memory
no point wasting 2x24h in build for these two.

Log message:
make it possible for gn to determine its own executable path so that
regenerating rules with ninja is possible

Log message:
update to 2020.11.85 and sync with the chromium port

Log message:
bump after libxslt dependency changed

Log message:
merge a missing patch from chromium which initializes fontconfig before
all the sandboxing in the renderer process to avoid hitting pledge violations

Log message:
remove the audio pledge from the audio process as direct audio device access it not possible anymore

Log message:
update to 2020.04.81

Log message:
get rid of more setpriority(2) to avoid pledge violations

Log message:
do not hardcode my pobj dir

Log message:
update to 2020.03.80 and sync patches with www/chromium

Log message:
fixup patches to not include my own pobj path

Log message:
update to 2019.11.78

Log message:
get rid of "parallel" in DPB_PROPERTIES on i386, just keep the "lonesome"

Log message:
Switch to PERMIT_PACKAGE.  CDROM restrictions are no longer applicable.

Log message:
bump REVISION in a bunch of ports known or likely to use struct kinfo_proc,
there may be some missing as my unpacked ports source is a little out of date
but this should catch the main things people might run into
the struct was reordered a second time in sysctl.h r1.192 to improve
compatibility but amd64 snapshot packages made it out before that happened
so the bumps are still needed

Log message:
sync WANTLIB

Log message:
sync patches with chromium

Log message:
set png16 WANTLIB entries back to png following the change in soname
part done by portbump, part by hand (it is easily confused)

Log message:
disable wasm (WebAssembly) by default because it is a disaster

Log message:
unbreak build by adding missing curly bracket

Log message:
update to 2019.04.73

Log message:
sync patches with chromium (v8 memory usage and pledge related)
ok sthen@

Log message:
add missing patches from previous commit that syncs sandbox code with chromium

Log message:
sync the sandbox code (pledge + unveil) with chromium

Log message:
set DPB_PROPERTIES+=lonesome on chromium/iridium for i386 (like is done
for firefox) in the hope that this will reduce build problems. these
ports often end up building together on a machine and they aren't coping
too well.
compiling some individual files is now bumping into my 75 minute DPB
stuck_timeout (possibly the llvm update took it over the edge) - raising
the timeout means that the other ports which occasionally hang during
compilation tie up a build slot for too long.

Log message:
fix theme handling by actually showing the necessary buttons in the settings
page

Log message:
add unveil(2) for /usr/bin/lpr to make the system print dialog work when
using lpr for printing

Log message:
Adjust () position to disable --build-id on OpenBSD. The patch file is
similar to one in chromium, but the line is slightly different meaning
this didn't work quite right. Fixes build with ld.bfd (e.g. i386 until
we switch to lld). ok robert@

Log message:
Allow text relocations on i386, caused by optimized non-PIC assembly in
the embedded copy of FFmpeg.  Chromium build test by sthen@,
looks good to robert@

Log message:
unbreak build by fixing two patches to not include my own pobj dir

Log message:
enable unveil(2) by default in iridium as well

Log message:
update to 2018.11.71

Log message:
unbreak i386 build by defining explicit WebVector(size_t size) : data_(size) {}
for non 64-bit arches on OpenBSD as well

Log message:
use the correct binary path to load the other processes

Log message:
unbreak build by adding a missing patch from the previous update

Log message:
update to 2018.11.70 and sync some changes with chromium

Log message:
so, special-casing openbsd is fun, but let's not forget dependencies...
fixes build breakage
okay robert@

Log message:
disable USE_LLD on i386, it still doesn't work there for these ports:
can't create dynamic relocation R_386_32 against local symbol in
readonly segment; recompile object files with -fPIC

Log message:
use jumbo build and use lld for linking just like in chromium

Log message:
introduce unveil(2) support for iridium by merging all the changes from
www/chromium
pass the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/iridium,
e.g.: /etc/iridium/unveil.main or /etc/iridium/unveil.gpu.

Log message:
@tag gtk-update-icon-cache

Log message:
first tag: update-desktop-database

Log message:
update to 2018.5.67

Log message:
update to 2018.4.66.0

Log message:
add a missing pledge related patch from chromium

Log message:
merge the user-agent patch from chromium and re-enable on i386

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
make iridium build with system clang as well by applying the same
patches as for chromium plus some extra due to the version differences

Log message:
use COMPILER_LIBCXX where applicable

Log message:
switch everything to new COMPILER idiom, even stuff that won't build with clang
yet, but at least that part is done.

Log message:
use the MODGCC4* variables instead of hardcoding dependencies.
convert to WANT_CXX even though it might not work yet.
bump the ports that didn't even the full spec

Log message:
update to 58.0

Log message:
stray whitespace breaks make syntax

Log message:
add missing build dependency for gtk+3

Log message:
remove bogous file

Log message:
update to 57.0

Log message:
update to 54.0

Log message:
Unbreak with cups>=2.2.0.
Hopefully catched all breakage since a few ports aren't building currently
(ligtop2...).

Log message:
use USE_WXNEEDED for chromium/iridium now that it works with gcc4

Log message:
add the required recvfd pledges

Log message:
add the -Wl,-z,wxneeded flag here as well

Log message:
add more mojom prebuild targets

Log message:
update to 51.1

Log message:
pre-build the autofill_server_proto target as well

Log message:
update to iridium-50.0 and sync recent changes with chromium

Log message:
update to 49.0

Log message:
oops

Log message:
droid-fonts -> noto-fonts

Log message:
Bump REVISION for lang/clang MODULE changes.

Log message:
security update to 48.2; ok sthen@ and naddy

Log message:
fix plist after the previous commit, sorry

Log message:
oops i accidentally disabled the pre-build targets, let's re-enable them

Log message:
update to 48.1 (based on the latest stable chromium which contains security
fixes as well)
ok naddy@ sthen@

Log message:
switch to libjpeg_turbo and merge the sandbox font handling patches from
chromium

Log message:
prebuild a missing dep that I ran into with chromium on a bulk build; ok robert@

Log message:
properly bump

Log message:
sync WANTLIB

Log message:
add an easily-greppable marker for ports known to use pledge().
it's not so important while they're only in patches in the ports tree,
but for any which get upstreamed it saves a ~100GB grep to find them.

Log message:
remove rpath from the GPU process's pledge call now that mesa has been taken care of

Log message:
pledge(2) iridium as well by syncing with the chromium port

Log message:
do not notify about tracker urls on the console and the browser
bar unless --trk is specified, it is just too much vomit for
a non-developer

Log message:
pretty-print the tracking addresses on the console

Log message:
add mojo bindings to the pre-build targets

Log message:
update to 47.0

Log message:
update to 47.0rc1

Log message:
remove devel/flex dep, these are ok with base flex

Log message:
pre-build gfx_vector_icons in chromium+iridium, ok robert@

Log message:
update to 46.0-final

Log message:
update to 46.0rc1

Log message:
unbreak build:

Log message:
detect *BSD in the javascript code of webui and sync the build hacks from chromium

Log message:
update to 44.1

Log message:
sync WANTLIB

Log message:
merge the patches from chromium that make iridium use the internal
libusb as well

Log message:
update to iridium-44.0 and also incorporate a patch from dcoppa@
for the startup script that still had references to chromium directories.

Log message:
update to 43.8

Log message:
allow iridium to restart itself when necessary after asking the user
for confirmation

Log message:
update to 43.5

Log message:
dependency fix, same as chromium

Log message:
update to 43.4

Log message:
Unbreak, REVISION cannot go backwards.

Log message:
update to 43.3

Log message:
add a missing build dependency to avoid ninja failing

Log message:
add a patch to avoid a crash on startup

Log message:
update to 43.2

Log message:
update to 43.1

Log message:
remove binutils hack

Log message:
Zap bogus '${SUBST_CMD}' line

Log message:
Our nm doesn't support neither '-D' nor '-f', hence some non-critical
errors occur during chromium and iridium builds:
---8<---
[2581/10537] CXX obj/components/policy/core/common/cloud/policy_component_common.cloud_external_data_manager.o
[2582/10537] CXX obj/components/policy/core/common/cloud/policy_component_common.external_policy_data_updater.o
[2583/10537] CXX obj/components/policy/core/common/cloud/policy_component_common.component_cloud_policy_service.o
[2584/10537] SOLINK(module) libffmpegsumo.so
nm: unknown option -- D
usage: nm [-aCegnoprsuw] [file ...]
[8618/16362] STAMP obj/extensions/extensions_browser.actions_depends.stamp
[8619/16362] AR obj/extensions/libextensions_browser.a
nm: unknown option -- D
usage: nm [-aCegnoprsuw] [file ...]
---8<---
Fix these errors by using llvm-nm instead.
While here, also fix a typo into iridium's pkg/DESCR (missing verb).
OK robert@ (maintainer)

Log message:
fix DESCR to fit in 80 columns, bump

Log message:
explicitly set DISTFILES, needed on i386

Log message:
add missing master_site, noted by naddy@

Log message:
update to iridium-browser-42.0

Log message:
add a backup master site