On Fri, Jul 31, 2020 at 06:09:53PM -0400, james wrote > and it builds, robustly and without errors, but is still dependent on > python 2.7. > > > so your details do result in palemoon 28.11.0 without python 2.7 > attendances?
Python 2.7 is still a build-time dependency. But rather than being provided by Portage, it's provided by the manually installed version. The manually installed version won't be touched by Portage. I have another idea. We already have firefox-bin and libreoffice-bin ebuilds where the compiled tarball is pulled down from upstream, and untarred. Would this work on Pale Moon? I guess it comes down to whether or not python 2.7 is a run-time dependancy as well as a build time dependency. I'll ask on the Pale Moon forum. If you want to go 100% manual you can actually pull down the tarball from http://linux.palemoon.org/download/mainline/ and extract it. Nice part is that you can pull down the tarball to say $HOME/pm/ and extract it, without root permissions. Point your program launcher to $HOME/pm/palemoon/palemoon (correct) and away you go. You can get fancy with multiple profiles. It doesn't splatter libs all over, so "uninstalling" consists of... rm -rf $HOME/pm/palemoon -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
