at least it's not like archlinux. i checked the way they do it in their package. they actually run a headless xserver with librewolf and they generate the profdata themselves. i think that's largely a waste of computer time, re-using pgo from mozilla makes sense since the code is nearly identical so nearly all of the profdata will match.
Am 31.08.26 um 14:26 schrieb [email protected]:
Le Mon, Aug 31, 2026 at 09:32:04AM +0100, Leah Rowe a écrit :Hi everyone, The attached patch does the following to the librewolf port: * Enable PGO on builds, by re-using Firefox PGO data. LibreWolf makes extensive modification to parts of Firefox, but most of the overall codebase remains unchanged. Most files remain unchanged in LibreWolf, so this PGO data will easily improve performance on LibreWolf as well, except on those parts that may differ substantially in LibreWolf, in which case the gain/loss would probably be zero. I'm unsure if any other project has ever tested building LibreWolf this way, but it does build, and it works perfectly. This should provide a notable performance increase depending on the user's workload. The LibreWolf port is version-matched to the FireFox port, and uses the same profile data that a corresponding FireFox version would in OpenBSD; since PGO already works there, we know it'll work in LibreWolf.while reusing PGO data is fine, i don't really see the point of changing DISTFILES.profdata (and having to make it ?= in moz.port.mk), setting FFDIST & FFVERSION since in all cases it wont share it with firefox as DIST_SUBDIR is set to something different, and it'll get fetched a second time with the same name but in that distinct DIST_SUBDIR. at that point.. oh well. i don't really care either way :)
-- 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
