I noticed there is a guy doing an official Pale Moon for Ubuntu package in an "unofficial" (i.e. Not directly authorized or managed by Ubuntu) repository he hosts himself, and he describes being largely able to do it with somewhat automated software based on the generic tarball or whatever that Pale Moon puts out.
I'm that guy. The packages are built from the source by the openSUSE Build Service in various generic distro virtual machines. OBS also automatically sets up a repository for the finished product and publishes it--I just upload the three debianized source packages. I now label the original source tarball as a "repack", since I have to extract the .7z source archive, run that chmod command on it, and then recompress it to a tar archive that the Debian build tools will recognize, and finally rename that archive with the exact syntax that they will accept.
Anyone with a Debian-based distro and a reasonably modern machine can rebuild my sources natively--do these all as a normal user, no root or sudo)
1: Install packaging-dev
2: Download the PM orig.tar.xz and debian.tar.xz files from here
3: Extract both archives in a PATH that has no spaces in it (no "My Build" folders)
4: put the debian folder into the extracted source folder, and enter the source folder.
5: open a terminal in that folder, and run
Code: Select all
debuild -uc -us -jX
(replace the "X" with the number of processor cores you want to devote to the compiling)
6: If you are missing any build-dependencies, it will fail and tell you what you are missing. Install those, and repeat the build command.
8. I noticed that 26.4.1 builds mysteriously and randomly fail about 10% of the time about 10% of the way through--when the .build file gets to about 2 MB--on both my laptop and on the OBS. In that case, re-extract the sources and try again. The mozconfig file used by the build lives in the debian folder--just edit it if you want to make any changes.
(off tangent: I tried adding the Debian hardening build flags, which is a really good idea for something with a big attack surface exposed to the Net, but that caused an early build failure due to an undefined "main" symbol being added to an object file. The hardening flags don't allow that to proceed. That's something only the developers can fix...)
Possibly the PM source could include a debian folder derived from the one I use--some other projects provide them, as well as files meant for rpm package builds. (see SMPlayer source for an example) Those would only add a couple K to the source archive.