Created attachment 219655 [details]
Here is a port of most of Pale Moon code with unofficial branding.
This port depends on the new Tauthon port I submitted here: bug #251019
Even when this dependency is imported, please *do not import the patch yet*. I'm in the process of liaising with upstream in order to verify that there is no branding or redistribution problems with the submitted port. I'll post a comment giving the go when the process finishes (the patch may need to be modified before reaching this point).
Small description: "Open-source web browser mostly using Pale Moon(TM) code"
The build needs some specific versions of GCC (executables crash with base clang on 12). GCC 9 was chosen since it is our current default and is (almost) officially endorsed upstream (and stability seems perfect so far). So USE_GCC is set, but then LDFLAGS and CXXFLAGS are appended to in order that g++ links to (base) libc++ (static link against libgcc.a). This is necessary since linking against libstdc++ while one of the dependencies is linked to libc++ causes a crash for this codebase. Also, gcc is removed from RUN_DEPENDS. See the comments in the Makefile (see also bug #211154).
Apart from jemalloc, all bundled libraries are used in preference to our versions in the ports tree. This is by design, and not bad by principle, and personally I won't dispute this precise case. See https://forum.palemoon.org/viewtopic.php?f=5&t=23706 for upstream's rationale.
So please wait until I confirm that the patch is final before importing into the tree. (And, obviously, please advise if you think the current Makefile is doing things wrong.)
The port could be effectively imported without problems, as it is not using official branding.
However, I'm trying to come closer to enabling it technically (not sure if activating it would be desirable).
Going also to clarify if there are more unofficial branding downsides, and how annoying they are.
So please wait while I'm resolving this.