[Suggestion] Mozilla Firefox ESR for Slackware 14.1
Suggestion for Slackware 14.1 browser with stability, security and long support in mind: Firefox Extended Support Release 24
ftp://ftp.mozilla.org/pub/mozilla.or...eases/24.0esr/ |
Quote:
|
Quote:
|
I would like to see Slackware keeping up with new Firefox releases. ESR is already available via SBo for anyone who wants to use that.
|
Quote:
|
Quote:
Thanks Patrick for update Firefox to 24 ESR in 14.1 Beta! |
ESR is an up to date version only for now, after the next release of Firefox it will miss features of the new versions.
I personally don't like the switch, for me that is a major drawback. For example, if Mozilla had decided to make 23 instead of 24 the ESR then the users of the ESR version never would have got H.264 video acceleration. |
Entirely agree. Whether the standard package is available in /extra or the ESR is in /extra; the option to choose here seems important.
|
I just switched to 24.0 ESR and things broke. I prefer ESR because I have to fix things less often, rather than every week or two.
|
Quote:
|
I just had to fix it again, just now, and that may not be the last of it. Most of the fixes are UI fixes. For example, for some unknown reason downloads didn't show up at all. I had to delete my profile and create it from scratch. Just now I found that the theme I was using somehow added close buttons to all my tabs in this version of firefox, so that had to be replaced.
This hassle is caused by Firefox devs copying Chrome and its release schedule. Stuff breaks all the time and I have to fix it the way it should be. I'm not going to do this every week or two, so I'm sticking to ESR. If nothing seems to break for you then continue doing what you are doing, however not long ago Pat V. had to switch to ESR because FF did really break: http://www.linuxquestions.org/questi...sr-4175467933/ |
If that was a bug in Firefox or in KDE is still not known, but I would assume that it was in KDE. At least PV reported it to KDE, not Firefox.
|
-infinity+1
I felt that the downgrade to 17.0ESR was a massive step backwards. It lost functionality and also became less stable to boot. As a result, I've started using Chrome more. With that said, I saw this in the -stable changelog: Quote:
|
i agree with TobiSGD, ill would also like to have the latest firefox.. not a fan of ESR here too.
|
Quote:
|
Quote:
|
It is not especially hard to repack the binary builds that Mozilla produces (I do it), so if you don't want ESR you don't have to use it. If you do repack rather than recompile the KDE/FF bug does not appear.
|
As far as I know the KDE/FF bug only appeared in 14.0, but not in -current, so this shouldn't be a problem anyway. The problem with repacking the binaries is that they are, AFAIK, not compiled with PGO, which means they come with sub-standard performance.
|
two small clarifications:
- the bug actually is between oxygen-gtk2 (the default gtk theme under kde) and firefox >= 22.0 on slackware64-14.0 (14.0 32bit and current/14.1 are not affected): it manifests also under xfce if you use the oxygen-gtk2 theme with it (firefox segfaults); - the binaries from mozilla are, AFAIK, built with PGO. |
Quote:
|
actually it is the Slackware binaries that are not compiled with PGO. from http://ftp.uninett.no/pub/linux/slac...fox.SlackBuild
Code:
# PGO is disabled by default: |
1 Attachment(s)
To use the non-ESR version of firefox I distilled the infrastructure from the xap/mozilla-firefox-24.0esr-x86_64-1.txz package into the attached package (rename .txt to .txz), the slack-desc of which reads:
Code:
mozilla-firefox-infra: mozilla-firefox (Mozilla Firefox Web browser) infrastructure Note that to install a new firefox version you just have to replace the /usr/lib64/firefox directory. Note too that the .tar.bz2 can also be a localized one. :D |
Quote:
www.panix.com/~ruari/latest-firefox |
Quote:
Quote:
Quote:
|
Quote:
:D |
Quote:
|
Quote:
|
Quote:
:D |
Because that is the entire point of blacklisting, to allow you to prevent slackpkg from manipulating packages you don't want it to touch. Blacklisting is already in wide use in the Slackware community. Why make a new system based on obscure naming, which seems flawed. Off the top of my head:
I'm not planning on changing my script in this regard but if you would like to use it and decide you would prefer go down the nonstandard name route by all means edit it locally. ;) |
OK, let us agree to disagree then.
Kind regards, Dick :D |
Quote:
|
Indeed it is pretty standard to tell the difference between an official package and a non official one by using a tags. Many people (myself included) use their initials, others use something that makes sense to them, e.g. AlienBob uses 'alien' and SlackBuilds.org uses '_SBo'. This makes it easy to blacklist groups of packages from the same author (or project). It seems pretty odd to introduce a new method when the current one has (and continues to) work pretty well after all these years.
EDIT: Tags also make it easier to list collections of packages by the same author/project. |
All times are GMT -5. The time now is 09:00 PM. |