So, the Slackware Team surrended in the front of RUST, and there is NO more modern Firefox packages for us?
What the heck happens with Firefox?
I know, I know, it is all about that RUST compiler, which does not compile itself, but always/anyways it can be put in /extra as repackaged binaries, just like we do with Java or FlashPlayer builds... Why I care about a more modern Firefox on slackware-current? Because of its ridiculous high optimization of the memory consumption in the latest releases (now 55.x). Long story short, where 52.3.x ESR wants 3.5GB memory (for a few hundred tabs, of course), the 55.x version wants around 500 MB. That's a goddamned difference! ;) |
is 55.x esr? if not, I do not want it.
|
I just download the 55.0.1 binary from Mozilla and extracted it to its own directory. It certainly is faster than 52.3. No doubt about it.
|
Quote:
I agree that may make sense to go ESR in a stable release, BUT the current stay on top of many other included software, anyways... If we want really those old good versions, maybe we should NOT jump always on the latest X.org, consequently breaking every time the AMD drivers, BTW... :D |
1. I thought the policy was (at least for a while) to have the latest Firefox for -current, and ESR for stable?
2. Slackware can always go back to repackaging the binary Firefox releases, which it did for years. |
FWIW Jean-Philippe Guillemin told me that he very much likes Firefox 55, especially as he gets a great sound from it, also better performances as others have said. He cares for that a he is also a musician.
You can get a package in this repo, should be OK on top of Slackware-current. In Slint I ship Mozilla-Firefox ESR (a repackaging). |
v55.0 has been out for 4 days. 4 days! And 55.0.1 was just released 2 days ago. If Pat does add it, he not only needs to build the newer version of Firefox, but also introduce rust into the system and all the testing that would need to go into that. Give it time...
And for any who are curious, the next ESR based on rust isn't expected until late Q1 2018, based on v59. |
BTW, "We cannot build the latest Firefox (meanwhile was 53.x) because the RUST doesn't compile itself" is a really old story, definitively not "only" 4 days old... ;)
Long story short, since 53.x we are stuck on ESR for current. How RUST looks being a showstopper, I propose to give it (to RUST) the same treatment on /extra, like the one given to Google Chrome: An user repackaged binary, if s/he needs it for real. |
Why not just use the binary package for the meantime? I expect the new Firefox will be added in some form in the future just like KDE 5 LTS because there is no announcement saying its going to be removed.
|
Quote:
I gave up on Firefox a while back, so I don't really care one way or the other. |
Thanks for the pointer. I installed the mozilla binary package in /opt and pointed /usr/bin/firefox to it. The new release feels a bit more snappy, so yeah i'll stick with it for now.
|
Quote:
I made this thread not for me, I am fine, thanks you!, but for others. ;) Quote:
WHY NOT TO JUMP RIGHT ON THE PLASMA SIX? :D BUT, this is a story for another thread... ;) |
Quote:
|
Darth, you are an interesting character. You demand the absolute latest versions of some things, but years/decades old versions of others. I guess that's where that saying comes from, "you can't please everyone."
|
That is nice of you Darth Vader. What I don't understand is why are you using Current when so many updates make you unhappy? The older versions of Slackware are still supported and don't contain the offending updates.
Plasma 6 LTS isn't released yet. They are still working on Plasma 5. There is no Qt 6. |
All times are GMT -5. The time now is 02:46 AM. |