Am 27.05.26 um 09:26 schrieb landry@openbsd.org:
> thanks,
>
> fwiw, this pending port isnt ignored, it's just that ppl have many
> things flying around, but hopefully it'll get reviewed in the coming
> days. being proactive about pending patches is nice, you can also check
> that it builds with ports-llvm 22, since i'm about to switch the wasi
> stack over for 22 and the mozs will follow.
>
> Landry

I appreciate it, thank you. Indeed, I'm aware that OpenBSD is a 
volunteer project with a heavy maintenance burden, especially in the 
ports tree. I come bearing zero entitlements, and I'm honoured simply to 
be acknowledged in this way.

I generally assume that whatever works for www/mozilla-firefox will also 
work for www/librewolf, since the codebase is very similar. Your 
patching touches Firefox in areas that LibreWolf does not modify, that 
also are not touched by other areas which LibreWolf modifies. In other 
words, I believe your change will work in LibreWolf.

The way I maintain LibreWolf is by treating your Firefox port as its 
upstream, adapting any all changes after you do, but on top of the 
LibreWolf tarballs instead. In this way, I maintain sync with your own 
efforts. This mirrors LibreWolf's own efforts with regard to Firefox, as 
their main priority is only to harden Firefox and not diverge too deeply 
from it.

When www/mozilla-firefox changes, www/librewolf will maintain in the 
same way. In so doing, we ensure that the only difference between these 
two ports are those changes which LibreWolf itself makes on top of 
Firefox. There are one or two minor exceptions, such as my patching of 
LibreWolf's build system which differs from Firefox (use of mozconfig 
which does not exist in Firefox). So the port logic is semantically 
equivalent, but not literally.

-- 
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 (3K)