Palemoon 28.17.0 binary file name change?

[BrianA_MN]

This is for the Linux file, but I wonder if the other files have the same issue. I notice the binary file was changed to include gtk2 after the x86_64 architecture. Will that remain? I run Slackware Linux and have modified Khronosschoty's build script, because it hasn't been updated since October. It worked without issue until this last update, which failed because of the file name change. FYI. Problem is solved, but will the name change again? Or is Palemoon going to be available in both a gtk2/3 and qt form in the future.

[New Tobin Paradigm]

Not QT but will see gtk3 soon and the extra designation has nothing to do with any system packages. Unfortunatly my good and dear friend Khronosschoty has been MIA for some time.

The change is needed for the generic binaries only to facilitate release engineering and application update services.

System packagers SHOULD only offer binaries using the gtk version (and arch) that is appropriate and predominate for their target distribution and version there in. Since we plan to offer gtk2 and gtk3 builds as generic binaries we need the additional designation.

The preceding is an authoritative answer on policy. The following is not.. yet.

I suppose the repacks as system packages are affected but those aren't true system packages tho. Different classification. Specifically classified as barely legitimate and lazy as hell and should be eliminated if possible in favor of EITHER true system packages built or getting users back on the generic binary with AUS train.

Repacks are an abomination that directly conflicts with both a true system package and our update service enabled generic binaries.