Pls. see my very fresh repo (since yesterday):
https://www.croatiafidelis.hr/foss/dev1miro/
and from the discussion at:
A Pale Moon repo for Devuan/Debian
viewtopic.php?f=37&t=18805
maybe it could suffice just the post most recent (at the time of this writing):
viewtopic.php?f=37&t=18805&p=138450#p138470
( if no reply for another while, the latest post will be my mozconfig that I will offer for approval, and that one will then be not anymore the last but the before last )
New to packaging. I'm trying to comply to be able to offer Pale Moon package for Devuan (and maybe some Debian folks might find interest to try it).
Moonchild wrote:
[...]
Then they still had the option to either make the changes to adhere to the license OR not use official branding but New Moon instead, and instead chose to just remove it from the portage tree.
I don't want to lose support, New Moon does not apeal to me. I want to comply.
And I'm using this topic to try and:
If anyone wants officially branded Pale Moon on...
[in my case Devuan, not on BSD]
I suggest you submit a proper portage addition that adheres to the license for official branding exceptions OR work with me to get an agreement on different build configuration if deviant build rules are desired that make it not comply with normally-accepted porting practices for packages.
I don't have any
--with-system-<this-or-that> which was the case in this BSD case, but my current mozconfig does depart a lot from the default.
I'm not an expert at all, but I did some packaging occasionally and with some reliability. Serving a real repo by Debian/Devuan policy is a first in my lifetime.
I have pretty clear concepts of possible deviations from the default in my mozconfig that I would like to do next, and my question is about those.
It's in that link, and it boils down, essentially, whether it is acceptable for Moonchild Productions to allow publishing Pale Moon package, and sources, with official branding, that would have all or most of the basic default options, but also these, I believe non-default options:
Code: Select all
ac_add_options --disable-dbus
ac_add_options --disable-pulseaudio
That's the core point that I need to ask.
New Tobin Paradigm wrote:@vingtzwanzig
There are a handful of packagers who do a great job working with us on building Pale Moon correctly for their target distros and users. Such as deu and his gentoo overlay,
I did use his overlay and his ebuilds a few times back some one and a half years ago... but I'm not on Gentoo since one year ago. Devuan I use now.
or Steve and his packages for all things remotely debian,
The thing here is the departure from systemd in Devuan, which is still remotely a debian Devuan distro, that's true of course.
And because of that departure (and SSL-key logging support in the browser) I have, for months now (
see: Building Pale Moon on Devuan fails
viewtopic.php?f=57&t=15751
) been building my own Pale Moon, and since yesterday started offering it to public.
IOW, while my builds are all based on Steve Pusser's work, I need those modifications, because his packages do not provide them... And not just me, but I'd believe most other Devuan users will like it better without pulseaudio and without dbus dependencies.
Yes there is great enthusiasm in Devuan for pure alsa, so no pulseaudio, as well as freedom from dbus.
Gentoo (and likely his, essentially, derivative Funtoo, and other derivatives) are currently I believe only distros that make it possible to run machines dbus free, e.g. without any of dbus programs, including libdbus and libgdbus libraries. I'd need to check, but I think it is close to complete purge of those...
Devuan is not completely dbus free (the libraries and not easily made redundant as in Gentoo), but is aspiring to become such...
So, would those
--disable-dbus and
--disable-pulseaudio in my next compilation for publishing in my repo void my permission to use:
Code: Select all
export MOZILLA_OFFICIAL=1
ac_add_options --enable-official-branding
would they void it?
My next mozconfig that I would like to try and build and publish will contain all from the link (and that is a paste):
http://developer.palemoon.org/Developer ... nfig_Files
Code: Select all
ac_add_options --enable-official-branding
export MOZILLA_OFFICIAL=1
mk_add_options MOZ_CO_PROJECT=browser
ac_add_options --enable-application=browser
mk_add_options MOZ_OBJDIR=/home/$USER/pmbuild/
ac_add_options --enable-optimize="-O2 -msse2 -mfpmath=sse"
ac_add_options --with-pthreads
ac_add_options --disable-installer
ac_add_options --disable-updater
ac_add_options --enable-release
ac_add_options --enable-devtools
ac_add_options --enable-jemalloc
ac_add_options --enable-shared-js
ac_add_options --enable-strip
ac_add_options --x-libraries=/usr/lib
Plus, I'd also include these lines:
Code: Select all
ac_add_options --disable-dbus
ac_add_options --disable-pulseaudio
and also:
These I would like to include too (however, I could go without them, but may not have enough knowledge at this time about them and the alternatives, nor what the defaults would be if these are not included
... ):
Code: Select all
ac_add_options --prefix=/usr
ac_add_options --enable-ffmpeg
ac_add_options --enable-fmp4
ac_add_options --enable-freetype
ac_add_options --enable-ogg
ac_add_options --enable-opus
ac_add_options --enable-png
ac_add_options --enable-svg
ac_add_options --enable-wave
ac_add_options --enable-webgl
ac_add_options --enable-webm
And in case it would prove necessary I would also include:
Code: Select all
ac_add_options --disable-precompiled-startupcache
but only if necessary.
I would really like to disable, if I may:
Code: Select all
ac_add_options --disable-safe-browsing
because (IIRC, that's google) it's more than anything an excuse for another bit in their mass surveillance, like most things google.
IIUC, would a mozconfig based on the above be acceptable to remain with official branding?
If not, what alternatives can you suggest?
Thank you for your kind consideration!