Hello, hope this is the right forum for my question:
every time a new version is available, it wants to replace the installed AVX build from test with the SSE2 one on updating.
Would it be possible to give the packages different names to prevent this?
Different package name for Pale Moon AVX?
-
- Posts: 97
- Joined: Wed Mar 30, 2022 4:15 am
Re: Different package name for Pale Moon AVX?
We are putting the AVX version in the test repo for now to keep it separate. Just refuse the regular upgrade and use MXPI to install the test repo version instead.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Re: Different package name for Pale Moon AVX?
Jost hold the one you want to get not upgrade withseriousness wrote: Sun Apr 13, 2025 4:26 am Hello, hope this is the right forum for my question:
every time a new version is available, it wants to replace the installed AVX build from test with the SSE2 one on updating.
Would it be possible to give the packages different names to prevent this?
Code: Select all
sudo apt-mark hold palemoon
-
- Posts: 97
- Joined: Wed Mar 30, 2022 4:15 am
Re: Different package name for Pale Moon AVX?
Thanks, I know how to work around this; it's just somewhat inconvenient...
Re: Different package name for Pale Moon AVX?
That's good. This is the way apt works, the latest (highest) version will be selected as installation candidate. Either set to hold current, or set a PIN priority accordingly to convince apt to keep a lower version.seriousness wrote: Sun Apr 13, 2025 11:34 am Thanks, I know how to work around this; it's just somewhat inconvenient...
Re: Different package name for Pale Moon AVX?
I think it's a better idea to get the updated browser with bugfixes, even if the first install will be non-AVX. Can you really tell if it's much slower?
Pale Moon is also really protective of its name, I don't want to go changing it right off.
Pale Moon is also really protective of its name, I don't want to go changing it right off.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
-
- Posts: 97
- Joined: Wed Mar 30, 2022 4:15 am
Re: Different package name for Pale Moon AVX?
I notice a slight improvement, but this could also be homeopathic...
Firefox and Vivaldi perform better without demanding for AVX.
Firefox and Vivaldi perform better without demanding for AVX.
Re: Different package name for Pale Moon AVX?
Would they object to palemoon-avx as a name though?Stevo wrote: Sun Apr 13, 2025 7:03 pm I think it's a better idea to get the updated browser with bugfixes, even if the first install will be non-AVX. Can you really tell if it's much slower?
Pale Moon is also really protective of its name, I don't want to go changing it right off.
It might be worth asking on their forum.
Re: Different package name for Pale Moon AVX?
Since the "palemoons" they provide are all avx already, I can see how they might object to that.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing