@MaddieM4 I have OpenBSD running on a few devices, but my main desktop is Void Linux. When I finally move it to OpenBSD I won't even bother with a dual boot, I'll just go all the way. And I'm close. Really, really close! Honestly just waiting on the LibreWolf port being worked on by @libreleah to be accepted into ports and I'm there.
@kaidenshi@MaddieM4 for now, you can just compile my librewolf port from source. i've been told that it won't be merged for 7.9. therefore, it would be merged for 8.0, and in the mean time merged into just -current once openbsd has fully reviewed it.
they're not taking new ports in the tree at the moment, because it's locked for a few weeks. they will presumably unlock the tree after the release, which i'm informed will happen some time in the middle of May.
@kaidenshi@MaddieM4 no need to figure out dependencies. just make sure if using my master branch to be on openbsd -current. i onyl maintain that branch for current. i'll start maintaining it in tagged releases from openbsd 8.0 onward, once openbsd merges my port in -current
@libreleah@MaddieM4 May is great, happy birthday to me! I've been trying to get your port to compile on my secondary workstation here at the house but I'm still trying to figure out dependency stuff (I am in no way, shape, or form a developer). I think I've managed to tackle every dependency except icu-i18n. If I can't get it to build on my own I'll just use your -current port once it hits the tree since I tend to run -current anyway.
@kaidenshi@MaddieM4 on my i7-4790k, the port takes about 12 hours to compile, which includes building dependencies. once dependencies are done though, building librewolf on its own takes maybe 2 hours?
@kaidenshi@MaddieM4 i'm contemplating whether to host a package repo for librewolf, for openbsd 7.9, since 8.0 is the first stable release that will receive my port. as i said before, they'll start merging new ports again in probably a few weeks. new ports are locked for now until the 7.9 release i think. that's the impression i got anyway. librewolf is the first openbsd port i ever did.
@libreleah@MaddieM4 Oh it's nothing wrong with your port, I just ran into issues building dependencies so I tried installing them as packages to both speed things up and avoid any compile issues, and that one package was being fiddly (the correct version from ports kept erroring out during compile, and (at the time I tried it the other day) the version in packages wasn't right).
Trying again right now with a fresh install of -current on my most powerful dedicated OpenBSD machine, hopefully this time it's all in place and it builds successfully.
@kaidenshi@MaddieM4 My port as it stands, that I submitted to the ports mailing list, is perfectly fine, though I want to tidy it up. LibreWolf largely applies the same config that OpenBSD applies to Firefox. Same hardening but much more patching of course.
It should be possible to unify both www/firefox and www/librewolf, making them both become rump configs relying on a larger, unified www/mozilla-browser module in the ports system. I asked landry about it earlier I think. Will look into it.
@libreleah@MaddieM4 That would be awesome and much appreciated! I still want to succeed at building it for my own personal achievement, but a pre-built package would be a boon to those of us who have been waiting years for a proper LibreWolf port. I feel like the intersection of OpenBSD enthusiasts and LibreWolf enthusiasts has to be wide and populous.
@kaidenshi@MaddieM4 The issue is that LibreWolf uses a mozconfig for configuration. I wanted to remain much closer to upstream, so my port ended up diverging quite a bit from the logic in www/mozilla-firefox.
However, I can do away with the mozconfig and configure everything directly from the ports system Makefile for www/librewolf. In this way, the port config would become virtually identical to www/mozilla-firefox, enabling me to unify both. Simple rules, and unify with www/mozilla-browser.
@kaidenshi@MaddieM4 I'll wait to see what landry says about the idea. If Landry gives the green light, then I will do it. I believe this would cause the least amount of friction and it would possibly enable to easy addition of other Mozilla FireFox forks in the future.
@MaddieM4@libreleah yep I saw that on the mailing list, I feel like that’s a sensible and efficient approach. I know Landry is not a fan of browser forks (reminds me of the Void Linux devs) but hopefully will be willing to work with you on it.
@kaidenshi@MaddieM4 The www/mozilla module is generic to all mozilla projects, not just browsers. So you have www/mozilla-browser doing the same generalisation for browsers. Someone joked to me in another thread that perhaps I could add GNU IceCat, not that I would be in any way interested, but someone could do that too. Perhaps the tor-browser port could be unified. Though Tor-Browser and IceCat both distribute plugin files, requiring more logic; LibreWolf bootstraps plugins via policy config.
@libreleah@MaddieM4 In other news, all dependencies satisfied on my current iteration, and the librewolf package officially started building at 20:08 local time. It's an HP mini pc with the i5-6600T so probably similar compile time to yours, if not a little slower. Fingers crossed!
@libreleah@MaddieM4 Okay yeah this 35W CPU is...not fast. This will probably still be building when I go to bed in a couple of hours.
But, this is the furthest I've gotten with it and assuming it builds correctly, tomorrow evening I'm backing up the main workstation and going full Puffy on the 5600GT. It should build in about 30 minutes on that relative beast.
@kaidenshi@MaddieM4 fun fact: you might sometimes have to compile it again, when updating snapshots. unless you idk stick to 7.9 (like, update to 7.9 from pre-7.9 -current before release). because openbsd doesn't do ABI-safety like on linux, so userland stuff will have to be recompiled when enough things change in kernelspace.
but enoughh of me being a debbie downer. congratulations!
@kaidenshi@MaddieM4 but lw doesn't change much. unless firefox does a new release. so i'd probably not worry about it, plus 7.9 is out soon. and also i assume they'll merge my port in -current at some point over the next few weeks. then you'll be able to just use the binary packages, so no worries.
@libreleah@MaddieM4 I backed up the package I built for safekeeping since it runs perfectly (actually a little faster than Firefox on the same machine). I tend to run -current so I'll just use your binary once it's merged.
@kaidenshi@MaddieM4 i also hardened some of the options at build time. you can see it in the git repository for my port. it's much closer to the hardening openbsd applies for firefox now, but with librewolf's additional hardening.
@Hello@kaidenshi@MaddieM4 You can control CPU frequency, check apmd manual. Or use obsdfreqd (i think it's called that). Probably still not as efficient as Linux, but you can get pretty close. I use the latter on laptops, when I'm out and about. obsdfreqd is in ports. You have to reconfigure apmd to disable some of its automation; check both manuals. Or just disable apmd when using obsdfreqd.
Also, I'll update librewolf soon. Got other work on at the moment. But will update the port after 7.9
@libreleah@kaidenshi@MaddieM4 Logged in after more than a year just to comment. THANK YOU SO MUCH for this. I very recently moved from linux to openbsd. Always used librewolf, and missed it on obsd. I am using -current branch, hopefully binaries are available soon! I have a thinkpad with i3, but runs a little hotter than on linux. On linux it uses like 7.5W and and on obsd it uses around 10-12 (even after experimenting with apmd -L and obsdfreqd). Not that bad though.