Different package name for Pale Moon AVX?

Message
Author
seriousness
Posts: 97
Joined: Wed Mar 30, 2022 4:15 am

Different package name for Pale Moon AVX?

#1 Post by seriousness »

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?

User avatar
Stevo
Developer
Posts: 14560
Joined: Fri Dec 15, 2006 7:07 pm

Re: Different package name for Pale Moon AVX?

#2 Post by Stevo »

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

User avatar
fehlix
Developer
Posts: 12698
Joined: Wed Apr 11, 2018 5:09 pm

Re: Different package name for Pale Moon AVX?

#3 Post by fehlix »

seriousness 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?
Jost hold the one you want to get not upgrade with

Code: Select all

sudo apt-mark hold palemoon
It will be shown as kept back package.

seriousness
Posts: 97
Joined: Wed Mar 30, 2022 4:15 am

Re: Different package name for Pale Moon AVX?

#4 Post by seriousness »

Thanks, I know how to work around this; it's just somewhat inconvenient...

User avatar
fehlix
Developer
Posts: 12698
Joined: Wed Apr 11, 2018 5:09 pm

Re: Different package name for Pale Moon AVX?

#5 Post by fehlix »

seriousness wrote: Sun Apr 13, 2025 11:34 am Thanks, I know how to work around this; it's just somewhat inconvenient...
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.

User avatar
Stevo
Developer
Posts: 14560
Joined: Fri Dec 15, 2006 7:07 pm

Re: Different package name for Pale Moon AVX?

#6 Post by Stevo »

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.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

seriousness
Posts: 97
Joined: Wed Mar 30, 2022 4:15 am

Re: Different package name for Pale Moon AVX?

#7 Post by seriousness »

I notice a slight improvement, but this could also be homeopathic...

Firefox and Vivaldi perform better without demanding for AVX.

User avatar
jeffreyC
Posts: 524
Joined: Mon May 27, 2019 10:39 am

Re: Different package name for Pale Moon AVX?

#8 Post by jeffreyC »

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.
Would they object to palemoon-avx as a name though?

It might be worth asking on their forum.

User avatar
Stevo
Developer
Posts: 14560
Joined: Fri Dec 15, 2006 7:07 pm

Re: Different package name for Pale Moon AVX?

#9 Post by Stevo »

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

Post Reply

Return to “Package Requests - MX-23”