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