Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
|
View Poll Results: Should future releases of Slackware include ESR versions of Firefox and Thunderbird?
|
|
Yes
|
  
|
60 |
63.16% |
|
No
|
  
|
35 |
36.84% |
 |
|
11-27-2012, 08:20 AM
|
#1
|
|
Member
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 771
|
Should future releases of Slackware include ESR versions of Firefox and Thunderbird ?
Hi,
I'm overall quite happy with Slackware, and I have a tiny suggestion to make here: why not replace the "general public" versions of Firefox and Thunderbird by their ESR counterparts ? In my humble opinion, this would "fit" the spirit of Slackware more, in the sense that the approach is more conservative, support for each release is about a year and a half, updates are simpler to manage (10.0.7 to 10.0.8, then to 10.0.9, and so on) while keeping all the add-ons compatible.
Here, I'm using FF and TB ESR since 13.37 and 14.0, built from slightly altered official SlackBuilds. Both work without any problems, and maintenance is a breeze.
So, I'm curious about your opinion. I've added a public poll to this post.
Cheers,
Niki
Last edited by kikinovak; 11-27-2012 at 08:24 AM.
|
|
|
|
11-27-2012, 09:42 AM
|
#2
|
|
Senior Member
Registered: May 2008
Posts: 2,843
|
I guess it all boils down to how well the mozilla devs maintain the ESR. The general release may be subject to a bunch of new bugs, but it'll also get all the latest fixes too. How much effort will be put into backporting them to the ESR? My gut feeling is that I'm better off following the general releases, but I'm not a heavy plugin/extension user so the api breakages don't really have much of an impact on me.
I would have clicked "Don't know" if the option had been there. 
|
|
|
1 members found this post helpful.
|
11-27-2012, 10:23 AM
|
#3
|
|
Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,610
|
I vote for ESR. I've tried Firefox ESR for a few months and haven't found any issues. I'd say it is safer to use ESR than the regular releases, especially because mozilla likes to shove these general releases out the door as quickly as possible even with major bugs.
|
|
|
2 members found this post helpful.
|
11-27-2012, 10:29 AM
|
#4
|
|
LQ Newbie
Registered: May 2012
Distribution: Slackware
Posts: 26
Rep: 
|
Personally, I like the rapid releases of Firefox. Also as GazL pointed out, I'm not sure how well bugfixes get backported to the ESR releases.
That's just my couple of pennies, though. Really, it's not a deal breaker for me either way. I've been gravitating towards Chrome lately anyway.
|
|
|
1 members found this post helpful.
|
11-27-2012, 10:37 AM
|
#5
|
|
Member
Registered: Feb 2010
Location: Chicago, IL
Distribution: Slackware64 14.0
Posts: 740
Rep:
|
Quote:
Originally Posted by dlachausse
Personally, I like the rapid releases of Firefox. Also as GazL pointed out, I'm not sure how well bugfixes get backported to the ESR releases.
That's just my couple of pennies, though. Really, it's not a deal breaker for me either way. I've been gravitating towards Chrome lately anyway.
|
I'd like to see Chrome replace Firefox as the default browser. I use Chromium personally, but that's probably too bleeding-edge for Slackware's taste. Chrome would be perfect. But if it's a choice between Firefox's latest release and ESR, I'd definitely say ESR.
Last edited by Cultist; 11-27-2012 at 10:39 AM.
|
|
|
1 members found this post helpful.
|
11-27-2012, 10:43 AM
|
#6
|
|
Member
Registered: Nov 2007
Posts: 268
Rep:
|
Quote:
Originally Posted by Cultist
I'd like to see Chrome replace Firefox as the default browser. I use Chromium personally, but that's probably too bleeding-edge for Slackware's taste. Chrome would be perfect. But if it's a choice between Firefox's latest release and ESR, I'd definitely say ESR.
|
Slackware cannot legally distribute a Chrome binary package. There is a slackbuild for Chrome in /extra. I would like to see Chromium as the default browser, Firefox ESR in /extra and the standard Firefox dropped altogether.
|
|
|
1 members found this post helpful.
|
11-27-2012, 11:19 AM
|
#7
|
|
Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,610
|
Ok, so to put an end to fears and assumptions:
Quote:
|
he ESR version of Firefox is for use by enterprises, public institutions, universities and other organizations that centrally manage their Firefox deployments. Releases of the ESR will occur once a year, providing these organizations with a version of Firefox that receives security updates but does not make changes to the Web or Firefox Add-ons platform. We have worked with many organizations to ensure that the ESR balances their need for the latest security updates with the desire to have a lighter application certification burden.
|
http://blog.mozilla.org/blog/2012/01...pport-release/
|
|
|
1 members found this post helpful.
|
11-27-2012, 11:52 AM
|
#8
|
|
Member
Registered: Sep 2012
Location: Bulgaria,Varna
Distribution: Slackware64
Posts: 178
Rep: 
|
Quote:
Originally Posted by kikinovak
Hi,
I'm overall quite happy with Slackware, and I have a tiny suggestion to make here: why not replace the "general public" versions of Firefox and Thunderbird by their ESR counterparts ? In my humble opinion, this would "fit" the spirit of Slackware more, in the sense that the approach is more conservative, support for each release is about a year and a half, updates are simpler to manage (10.0.7 to 10.0.8, then to 10.0.9, and so on) while keeping all the add-ons compatible.
Here, I'm using FF and TB ESR since 13.37 and 14.0, built from slightly altered official SlackBuilds. Both work without any problems, and maintenance is a breeze.
So, I'm curious about your opinion. I've added a public poll to this post.
Cheers,
Niki
|
Could you upload your slackbuild,for mozilla esr
|
|
|
|
11-27-2012, 12:13 PM
|
#9
|
|
Member
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 771
Original Poster
|
Quote:
Originally Posted by tuxbg
Could you upload your slackbuild,for mozilla esr
|
The SlackBuilds for the l10n packages only build french and german language packs, but they can easily be edited for other languages.
I'm lagging behind one or two minor versions, but then again, just change the version number in the script for the latest and safest.

Last edited by kikinovak; 11-27-2012 at 12:15 PM.
|
|
|
3 members found this post helpful.
|
11-27-2012, 01:15 PM
|
#10
|
|
Member
Registered: Jun 2008
Posts: 168
Rep:
|
I'm fed up as well with the quick release cycle of both FF and TB lately. I've nothing against them releasing daily versions if they want - but keep them on minor version numbers. There has always been a very good reason why we had major and minor version numbers. This madness with changing major version numbers faster than socks (the wooly types - not the others  ) and breaking all sorts of things in the process is just a senseless industry fad. I hope some reason is restored sooner rather than later. Open Source / Free Software didn't use to suffer so much from the smokes, mirrors, trickery and self servitude of marketing departments - and instead concentrated on the real needs of users. That, unfortunately, seems to be changing.
|
|
|
|
11-27-2012, 03:50 PM
|
#11
|
|
Member
Registered: Dec 2008
Posts: 745
Rep: 
|
Quote:
Originally Posted by GazL
I guess it all boils down to how well the mozilla devs maintain the ESR. The general release may be subject to a bunch of new bugs, but it'll also get all the latest fixes too. How much effort will be put into backporting them to the ESR? My gut feeling is that I'm better off following the general releases, but I'm not a heavy plugin/extension user so the api breakages don't really have much of an impact on me.
I would have clicked "Don't know" if the option had been there. 
|
I am not quite fond of the security fixes, if you meant this. I simply don't like things be broken every now and then.
Had to switch to esr after upgrading to Slackware-14.0 because nothing could prevent Firefox 15 from crashing on my machine. (Of course I tried creating new profiles.)
|
|
|
|
11-27-2012, 04:15 PM
|
#12
|
|
Member
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 116
Rep:
|
I think it would be nice to include ESR SlackBuild-scripts in /extra. That way users have a choice.
|
|
|
5 members found this post helpful.
|
11-27-2012, 04:30 PM
|
#13
|
|
Member
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 771
Original Poster
|
Quote:
Originally Posted by mats_b_tegner
I think it would be nice to include ESR SlackBuild-scripts in /extra. That way users have a choice.
|
I know the guys from SlackBuilds.org don't generally accept builds that replace existing Slackware packages in another version. I wonder if they would make an exception for these two.
|
|
|
|
11-27-2012, 05:06 PM
|
#14
|
|
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 2,784
|
Quote:
Originally Posted by kikinovak
I know the guys from SlackBuilds.org don't generally accept builds that replace existing Slackware packages in another version. I wonder if they would make an exception for these two.
|
Just ask 
|
|
|
|
11-27-2012, 05:26 PM
|
#15
|
|
Member
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 503
Rep: 
|
I wouldn't mind seeing them in /extra.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 07:23 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|