Le 30/03/2018 à 16:28, Steve Litt a écrit :
On Thu, 29 Mar 2018 17:42:37 +0200
Jaromil <[email protected]> wrote:
hi Chillfan,
On Thu, 29 Mar 2018, Chillfan wrote:
I agree that a fork is needed, but I think this would be a whole
lot of work.
yes. forks are a LOT of work. Even Devuan, which I'd say is a
relatively easy fork, mostly needing work on the infrastructure and
testing and documentation side, was more demanding than expected.
If palemoon offered something akin to extended support releases it
would be a great candidate for that,
palemoon is stuck at "version 27" series of Firefox and in any case
its in the 2x series I doubt it can be brought up to 50 since the
codebase is rather different.
said that, I'm happy with palemoon, using always the latest stable
release tagged on the git tree, compiling it myself on Devuan and then
github.com/dyne/tinfoil for sandboxing. here the mozconfig I use,
please note I do not disable pulseaudio or dbus, because that gives
problems, yet I do not use pulseaudio (but I do use dbus...)
Here's why I wouldn't use Palemoon if it were the last browser on earth:
https://github.com/jasperla/openbsd-wip/issues/86
By the way, a little research on USPTO shows they have no registered
trademark on "Palemoon". For somebody so lawyerly threatening, he sure
hasn't dotted his i's and crossed his t's.
This sheds a bad light on the whole project, but maybe they're
forced to do so because they inherit the source and the build system
from Mozilla.
Anyway, you're normally don't want the distributed package because
it depends on things you don't want, like Dbus and Pulseaudio. So just
download the source from the official website and build with the config
you like. Don't "distribute" the binary and forget the licensing crap.
Didier
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng