Re: librewolf port

[Leah Rowe]

So..... here's how I maintain the port:

First, I adapt all changes to the FireFox port







build it. see if it's all kosher

then do

make update-plist

make update-patches (for shits and giggles)

then i build it again





usual stuff

librewolf has tarballs on their codeberg releases page

good luck

don't worry if you fuck up. i'll be back in a few weeks.



Am 16.07.26 um 21:42 schrieb ya...@protonmail.com:

I check upstream mozconfig in librewolf, for changes, adapting those changes into mozconfig-openbsd in the port i check for upstream changes to the policy json file that the port also patches. i adapt/rebase those yeah then just check if it compiles, after all the usual stuff like... change the hash of the new tarball, size etc then all is well in the universe, and i submit the patch, once i confirm it compiles and runs i normally test a few features too e.g. webgl(disabled by default but can be turned on), webrtc, various video streams, and so on.

På torsdag 16. juli 2026 kl. 15:33, skrev Leah Rowe
<i...@minifree.org>:

yeah, you seem competent. you always seemed to submit identical patches
too, when i was doing it a few weeks ago.

i hereby make you my deputy. you can fill in for me. i'll be back in a
few weeks.

i was ill during june and i'm catching up on other shit this month. no
time for openbsd. i'll be back in like, mid to late august probably.

I can do that and work with the rest of the ports team.

May you stay healthy and successful in your catch up and other stuff. 👍


På torsdag 16. juli 2026 kl. 17:30, skrev Caspar Schutijser
<cas...@schutijser.com>:

Do you mean the changes to www/mozilla-firefox/files/policies.json
on July 1st or something else? Either way, I looked at those changes
in mozilla-firefox and I'd have to look into the Librewolf port a bit
more to be sure how to apply that to Librewolf. In the interest of time
I'll leave that alone for now. Worst case, Leah can have a look once
they're back.

Caspar

Ah, I meant www/librewolf/files/mozconfig-openbsd which, if I understand
correctly, is one of the mechanism by which the librewolf project
changes or adjusts compile/runtime flags of the firefox upstream. Like
hardening, turning off AI, disabling telemetry, toggling privacy
features, and other changes. This is mirrored somewhat by the
arkenfox(previously ghacks user.js) project and www/mozilla-firefox in
tree already includes many(not all) of these adjustments, particularly
security ones.

Firefox sometimes includes features or new/renamed toggles between
updates that librewolf turns off, transitions when removed/renamed or
changes default values for flags so one doesn't manually have to slough
through various hidden or poorly documented values and apply them in
the about:config page. More security, privacy, and turn off new features
while allowing people to opt in manually by default compared to
upstream, or at least that is what librewolf project professes to do.

I think policies.json added the disable AI and another (mis)feature that
Leah already had in the mozconfig-openbsd. So probably no worries on
that front at least.

Yeah, I agree Leah can look at the mozconfig-openbsd when they're back.
Leah did a lot of that work in her initial port and has adjusted that
since, so I feel more comfortable waiting for that knowledge base and
expertise.

Thanks to you(Caspar) and Landry for the commit and may you all have a
good one too. :D Night.
--
yaydn

--
Company director, Minifree Ltd
Registered in England, No. 9361826 | VAT No. GB202190462
Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK

OpenPGP_0x5C654067D383B1FF.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature