[SOLVED] So, the Slackware Team surrended in the front of RUST, and there is NO more modern Firefox packages for us?
SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It was never an expectation that a fresh Slackware install would be capable of rebuilding all of its packages.
Isn't that literally the point of the sources DVD? You can recompile any included software using just the full Slackware install and the sources. Thats the impression I got from the main site, SlackDocs, manual pages, etc.
Isn't that literally the point of the sources DVD? You can recompile any included software using just the full Slackware install and the sources. Thats the impression I got from the main site, SlackDocs, manual pages, etc.
I agree, that would be a departure from the norm. As far as I know, any of the Slackware sources should be rebuild-able with a full Slackware install and nothing more (though I've never tried rebuilding all of them, so I could be wrong).
ESR stands just for Extended Support Release, nothing magic here, you know...
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...
see ESR more as a LTS, and the other one, firefox current, as a developer snapshot. No magic here.
if you put a non LTS into current, and than want to stabilize for release, you might what to go down with the version number, or ship an unstable package with Slackware, or adopt to the release cycle of the whole distribution to the release cycle from FF.
So this is a different situation to your comparison with xorg, no magic here, just details, BTW ...
also, and this is why i prefer ESR, ff-current breaks plugins from time to time, and I know a lot of users that have changed because of this to chrome.
Mozilla made a huge mistake by making their current branch to the 'default' one, and the ESR to only those who know about it.
It should have been precise vice versa, than firefox would not have that big loss on users, which hey have.
Mozilla made its users to beta testers, and frustrated a lot of plugin authors with their unstable and unpredictable development plans. The shrinking user numbers are the result.
Isn't that literally the point of the sources DVD? You can recompile any included software using just the full Slackware install and the sources. Thats the impression I got from the main site, SlackDocs, manual pages, etc.
Quote:
Originally Posted by montagdude
I agree, that would be a departure from the norm. As far as I know, any of the Slackware sources should be rebuild-able with a full Slackware install and nothing more (though I've never tried rebuilding all of them, so I could be wrong).
As far as I know, that's a misconception. I'm going by this quote from Pat:
Quote:
We give you the exact sources that were used to compile the packages. There's no guarantee that these sources will compile under any arbitrary development environment (including any particular version of Slackware).
Firstly, to note that we talk about a particular web browser, and is generally considered that for web browsers the latest versions are the best. Always.
That is factually incorrect, especially with regard to Firefox. Some releases are better than others, and it's seldom a linear progression.
Okay, now that I looked at that thread I remember that I've heard that before. However, I still think it would be a departure from the norm for a SlackBuild script to require a certain compiler but for that compiler to not be available on Slackware at the time the package is built.
I stand corrected. Makes sense. (The thread that link is for is RIDICULOUS)
Ah, that asshole LuckyCyborg... I used the occasion to add a bit of explanatory text to the Slack Docs FAQ page: https://docs.slackware.com/slackware...d_from_scratch . I hope that it is sufficient to fend off any future trolls.
Then, how you explain that three major versions later, same software manage to do the same job using around 500MB ?
Do add-ons like uMatrix, uBlock Origin and Tree Style Tabs work with this latest Firefox? They're the reason I use Firefox. Memory use is not an issue for me because I have 32GB but the plugins definitely are an issue. Perhaps Pat has this in mind?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.