I successfully built pale moon and basilisk on openbsd without system libraries

[librecat]

only 2 small patches needed in uxp and the browser seems to be stable would you mind upstreaming them(i debranded my modified pale moon source tree with basilisk without sync support to be responsible)

edit: missing features include webrtc and gamepad(requires writing openbsd specific code which i cant do)

[Moonchild]

If you want this upstreamed you'll have to make sure to not hard-require gtar instead of tar.
You may have to parameterise the tar command and select the appropriate one based on OS.

[librecat]

sure, i will make it based on environment variable. thanks for the help and kindness

[Moonchild]

I hope you do understand that our way of building goes against OpenBSD's philosophy surrounding software, so you may run into a lot of resistance when trying to advocate its use in the OpenBSD community. That's not a fight I will get involved in again.

[librecat]

i forgot to say this needs more work like writing sndio and openbsd networking code to fix webrtc
edit: also pledge and unveil support

[librecat]

yes i am aware from reading older posts, my plan is to use this for personal use like on freebsd with a binary tarball

[librecat]

im terrible at being responsible and sticking to a project so dont expect any support from me

edit: maybe this can be clarified with no support openbsd build instructions
edit2: or i just private the repos until its ready and i want to provide support
edit3: i decided to private them on my own

[librecat]

i read enough forum posts to be tired of half baked ports that only create drama or re ignite it so im privating it

Off-topic:
this drama benifits nobody so its best to avoid it from the start

[Moonchild]

If you don't plan to support it and it's for private use only and you're not distributing, then you're free to do whatever you want (including building with official branding).
If you want to do that, make sue you include --enable-private-build in your .mozconfig (so any accidental distribution is marked appropriately as a private build). This has no impact on its operation otherwise.
Do note that WebRTC isn't supported in Pale Moon, and building with it will cause issues for WebRTC use (e.g. no UI controls). You may want to opt for building basilisk instead if you want WebRTC usage, for its limited support.

[librecat]

thanks for mentioning --enable-private-build, i will probably unprivate the repos if i decide to give support

[librecat]

pale moon built without issue, basilisk did not build even when disabling webrtc, i copied the application code into the pale moon source tree and built it with the pale moon mozconfig and that seemed to work so as a final step i decided to rebrand this as iceweasel-uxp after letting the hyperbola project know because i wanted to share this with hyperbola initially

[librecat]

i could unprivate the repos if i do this?

.mozconfig:
# not ready for public use yet
ac_add_options --enable-private-build

[Moonchild]

I don't care about the repos being public or not. It's Open Source, after all
This matters for binaries you build if using official branding, only.

[librecat]

ok got it

[frostknight]

ok got it

I have a patch i use to build in Hyperbola, it could potentially be used to further debloat the browser if you are doing it via new moon.

https://upload.disroot.org/r/C59xtX3f#a ... 2HrNv7k0I=

some crap like dbus is disabled in this patch I have. Not sure which patches are applicable and which aren't though.