10:47 <beerman> farkuhar care to adopt firefox?

10:57 <farkuhar> beerman: it's a tempting idea. I would have to run at least two costly build jobs, every time a new version comes out. But by reverting to a "non-fluid Pkgfile", I could get away with only one test build.

11:01 <farkuhar> I'm currently taking this browser build for a test drive: https://pasteboard.co/IQZhLE4gC0kO.png (apologies to SiFuh for sharing via an ad-infested site)

11:05 <SiFuh> farkuhar: Wasn't so much as the adds but the forceful acceptance of cookies and clicking boxes and ticking stuff, just to look at something

11:06 <SiFuh> farkuhar: you URL i'd paste it like this https://gcdnb.pbrd.co/images/IQZhLE4gC0kO.png

11:48 <beerman> i don't care either way, its just that i was tempted to mark firefox and the wasi builds as unmaintained as people ran into erros with it over at #crux-arm and I feel like danny is gone again for the next extended period of time

11:54 <beerman> anyway, cleaning out the unmaintained ports from opt/contrib seems like a first step, marking others unmaintained the next

12:01 <farkuhar> it was actually by reading the comments in #crux-arm that I got the idea to mark the wasi stuff as optional dependencies. The other build that I'm testing had --without-wasm-sandboxed-libraries in its mozconfig.

12:04 <beerman> i have no idea if thats smart or not

12:09 <farkuhar> it's a pretty standard choice, considering r0ni's comment about the Slackware FF package, and the mozconfig templates I found at voidlinux and BLFS.

12:11 <beerman> the important part is to maintain it, and danny is not maintaining anything right now. thats what i care about

12:18 <farkuhar> well, I'll be testing my two FF builds to see how they handle regular usage. If I run into any problem, I'll try to identify whether it's an upstream issue, or something that can be fixed in our port.