LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-19-2021, 05:07 AM   #8191
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,303

Rep: Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016

Quote:
Originally Posted by GazL View Post
The inference is clearly that Slackware 15.0 will be sticking with the ESR going forwards, otherwise there'd be no reason to mention and smiley-face it.

Barring any confirmation of intent, I guess we'll find out for certain when firefox moves to 92 and Slackware 15.0 doesn't.
Why didn't he include it when it was released then?
 
Old 08-19-2021, 05:16 AM   #8192
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,889

Rep: Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010
Quote:
Originally Posted by marav View Post
Why didn't he include it when it was released then?
Perhaps Pat is waiting for the ESR to diverge from the mainline before branding it as such. Only he knows his intentions at this point. I can only state my interpretation of the changelog comment: YMMV.

Last edited by GazL; 08-19-2021 at 05:18 AM.
 
Old 08-19-2021, 05:23 AM   #8193
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,966

Rep: Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540Reputation: 1540
Quote:
Originally Posted by GazL View Post
The inference is clearly that Slackware 15.0 will be sticking with the ESR going forwards, otherwise there'd be no reason to mention and smiley-face it.

Barring any confirmation of intent, I guess we'll find out for certain when firefox moves to 92 and Slackware 15.0 doesn't.
This is a distinct possibility but based on comments in the change logs when we went back to Firefox proper I'm guessing we will stick with that and not the ESR release. I could be wrong of course.

Code:
Mon Mar 15 19:37:28 UTC 2021
<<snip>>
xap/mozilla-firefox-86.0.1-x86_64-1.txz: Upgraded.
       When we first moved Slackware to the Firefox ESR channel, the motivation
       was to keep Firefox secure while delaying a requirement for Rust at build
       time. Of course, eventually that ESR version reached EOL and we had to
       introduce Rust into Slackware 14.2 in order to continue providing updates.
       Eventually that also ran into roadblocks as Firefox required first newer
       C/C++ compilers, and then finally a newer libstdc++. To continue, we'd
       have had to bump GCC to a much newer version, making other maintenance
       difficult or impossible. At this point, the latest Firefox has no additional
       dependencies beyond those of the ESR version, and it's unlikely that it
       will be any more difficult to keep it maintained. I think we all want the
       Slackware 15.0 release to be as good as possible, and most users will be
       better served if we resume following the latest desktop releases.
       Thanks to LuckyCyborg who can always be counted on to give me a friendly
       kick in the rear end. :-) Thanks also to ponce for the updated gkrust patch.
 
Old 08-19-2021, 05:30 AM   #8194
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,303

Rep: Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016
Quote:
Originally Posted by chrisretusn View Post
This is a distinct possibility but based on comments in the change logs when we went back to Firefox proper I'm guessing we will stick with that and not the ESR release. I could be wrong of course.
That's why :
https://www.linuxquestions.org/quest...ml#post6276348
 
Old 08-19-2021, 05:48 AM   #8195
avian
Member
 
Registered: Aug 2014
Posts: 184

Rep: Reputation: Disabled
Thanks for that, didnt know there was a public git repo for slackware source. Very helpful.
 
Old 08-19-2021, 08:45 AM   #8196
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,469

Rep: Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266
Quote:
Originally Posted by chrisretusn View Post
This is a distinct possibility but based on comments in the change logs when we went back to Firefox proper I'm guessing we will stick with that and not the ESR release. I could be wrong of course.

Code:
Mon Mar 15 19:37:28 UTC 2021
<<snip>>
xap/mozilla-firefox-86.0.1-x86_64-1.txz: Upgraded.
       When we first moved Slackware to the Firefox ESR channel, the motivation
       was to keep Firefox secure while delaying a requirement for Rust at build
       time. Of course, eventually that ESR version reached EOL and we had to
       introduce Rust into Slackware 14.2 in order to continue providing updates.
       Eventually that also ran into roadblocks as Firefox required first newer
       C/C++ compilers, and then finally a newer libstdc++. To continue, we'd
       have had to bump GCC to a much newer version, making other maintenance
       difficult or impossible. At this point, the latest Firefox has no additional
       dependencies beyond those of the ESR version, and it's unlikely that it
       will be any more difficult to keep it maintained. I think we all want the
       Slackware 15.0 release to be as good as possible, and most users will be
       better served if we resume following the latest desktop releases.
       Thanks to LuckyCyborg who can always be counted on to give me a friendly
       kick in the rear end. :-) Thanks also to ponce for the updated gkrust patch.
Exactly! The Man said clear his intentions and his reasons. With a lengthy explanation.

But, some people was hit so hard on their beliefs that Firefox for Enterprise must be on Slackware, so they embrace that hard a remark, like someone drowning a stick.

However, there is a much more plausible reason for this remark: the MozJS package is built from the Firefox for Enterprise sources.

So, right now we have mozjs78-78.13.0esr-x86_64-1.txz and is quite plausible that in the near future it will be upgraded to mozjs91-91.0.1esr-x86_64-1.txz or something similar, because of that "New ESR release :-)"

Last edited by LuckyCyborg; 08-19-2021 at 10:44 AM.
 
2 members found this post helpful.
Old 08-19-2021, 10:55 AM   #8197
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by LuckyCyborg View Post
But, some people was hit so hard on their beliefs that Firefox for Enterprise must be on Slackware, so they embrace that hard a remark, like someone drowning a stick.
*onto my soapbox*

And some want Slackware to consistently introduce potentially disrupting packages into a stable release.

There is no happy medium. No matter what way Pat chooses to go, someone will be disappointed. I am of the belief that a stable release should be stable and introducing potentially disrupting official packages is not ideal and should only happen when necessary (like if a branch becomes unsupported upstream, but we really needed fixes and it is too much to backport).

If someone wants the new features from Firefox, it is *really* easy to use ruario's script to repackage the official binaries. Since pure-alsa was removed, that makes it even easier to use his script. It even defaults to the desktop release.

If someone wants a newer kernel, it's pretty straightforward to build your own nowadays.

My belief is not from a standpoint that everyone should be running these long term support versions, but that switching away from them should be a choice made by the admin of the system (which I've done for my systems many times). For those using the official packages, they should be able to upgrade them without worry that they're going to have drastic changes unless there's no other way (and then it should be covered on the ChangeLog, like when openssh was upgraded and changed the default for root login).

Keep the potentially disruptive packages in -current.

*off my soapbox*

I'm not personally bothered by these and will continue to use Slackware as I please, but it seems to go against the philosophy of "stable" releases that Slackware has seemed to follow in the past.
 
3 members found this post helpful.
Old 08-19-2021, 11:16 AM   #8198
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,889

Rep: Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010Reputation: 5010
Quote:
Originally Posted by bassmadrigal View Post
Since pure-alsa was removed, that makes it even easier to use his script. It even defaults to the desktop release.
The lack of alsa support is annoying, but easily worked around with apulse.

I use this wrapper script on my CRUX box(which uses mozilla's binary build):
Code:
$ cat usr/local/bin/firefox 
#!/bin/sh

# Uncomment and change the following if you want to specify
# a specific ALSA audio device.
#export APULSE_PLAYBACK_DEVICE='default'

exec /usr/bin/apulse /usr/bin/firefox "$@"
Never had any issues using it.
 
1 members found this post helpful.
Old 08-19-2021, 11:32 AM   #8199
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,303

Rep: Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016Reputation: 4016
Quote:
Originally Posted by bassmadrigal View Post

I'm not personally bothered by these and will continue to use Slackware as I please, but it seems to go against the philosophy of "stable" releases that Slackware has seemed to follow in the past.
Firefox desktop is not less stable than ESR Edition

Firefox ESR is focused on a very specific audience :
users who do not want or cannot update every few weeks.
91.1esr will only be released when 92.0 will be out
91.2esr, with 93.0
….
92.0esr, with 101.0 (?)

This cycle of release is very suitable for the corporate environment

Last edited by marav; 08-19-2021 at 11:46 AM.
 
Old 08-19-2021, 01:19 PM   #8200
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Rep: Reputation: Disabled
Here's a idea, START A NEW THREAD TO TALK ABOUT GARBAGE LIKE FIREFOX. It's a miracle that any actual "requests" get seen here.
 
3 members found this post helpful.
Old 08-19-2021, 01:26 PM   #8201
saxa
Senior Member
 
Registered: Aug 2004
Location: Nova Gorica, Salvador
Distribution: Slackware
Posts: 1,210

Rep: Reputation: 295Reputation: 295Reputation: 295
glib-2.68.4
https://download.gnome.org/sources/g...-2.68.4.tar.xz
 
Old 08-19-2021, 01:47 PM   #8202
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 144

Rep: Reputation: 236Reputation: 236Reputation: 236
A pending issue that I already reported sometime ago: since the introduction of PAM, mariadb comes with the file /etc/security/user_map.conf. Unfortunately it is not installed as a .new file, so any user-changes will be overwritten on every update! There is no need to force an update of this file as the original only contains comments.

Last edited by Markus Wiesner; 08-19-2021 at 01:50 PM.
 
1 members found this post helpful.
Old 08-19-2021, 04:22 PM   #8203
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,469

Rep: Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266Reputation: 3266
Mesa 21.2.1

https://lists.freedesktop.org/archiv...st/225464.html

https://mesa.freedesktop.org/archive/mesa-21.2.1.tar.xz
https://mesa.freedesktop.org/archive...2.1.tar.xz.sig

Mesa 21.2 introduced the Intel "Crocus" Gallium3D driver for i965 through Haswell graphics hardware support, PanVK was merged for starting on Vulkan for Arm Mali GPUs, support for alternate GBM back-ends contributed by NVIDIA, continued work on Intel Gen12/Xe Graphics across the board, various RADV Vulkan driver improvements, and much more.

Those "alternate GBM back-ends" means a huge improvement for the Wayland on NVIDIA and Intel Crocus (at least for me) looks working better and faster than the "classic" Intel driver on HD2000 hardware given by my i3 2120T and i3 3220T. It's kinda of Iris Legacy.

Last edited by LuckyCyborg; 08-19-2021 at 04:28 PM.
 
2 members found this post helpful.
Old 08-19-2021, 07:20 PM   #8204
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,331

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
Hello , i think the konsole build 2 , have bad patch , when no config , initial size are wrong (like 1st run) , i found the 2 original commits and patches for this.

Our patch is only 1 file , i dont know if a "try merged" or what , but not good , there are the originals.

https://invent.kde.org/utilities/kon...41587137.patch
https://invent.kde.org/utilities/kon...bc06c5ab.patch

I really interested on this one , read explanations... and please , apply

From c78edfbac49852cec40efd5cbe73c341bc06c5ab Mon Sep 17 00:00:00 2001
From: Ahmad Samir <a.samirh78@gmail.com>
Date: Thu, 29 Jul 2021 18:45:45 +0200
Subject: [PATCH] Fix MainWindow size when there is no saved size

The very first time a user runs Konsole, where is no konsolerc file in $HOME,
there is no saved size to restore, instead use the sizeHint(), which ideally
will be the size set in the default profile (based on lines/columns setting).


https://invent.kde.org/utilities/kon...bc06c5ab.patch

EDIT: I test the patches and all is fine , tollbars and initial size on first run.

Last edited by USUARIONUEVO; 08-19-2021 at 07:31 PM.
 
1 members found this post helpful.
Old 08-19-2021, 09:03 PM   #8205
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,179

Rep: Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376Reputation: 1376
Quote:
Originally Posted by USUARIONUEVO View Post
Hello , i think the konsole build 2 , have bad patch , when no config , initial size are wrong (like 1st run) , i found the 2 original commits and patches for this.

Our patch is only 1 file , i dont know if a "try merged" or what , but not good , there are the originals.

https://invent.kde.org/utilities/kon...41587137.patch
https://invent.kde.org/utilities/kon...bc06c5ab.patch

I really interested on this one , read explanations... and please , apply

From c78edfbac49852cec40efd5cbe73c341bc06c5ab Mon Sep 17 00:00:00 2001
From: Ahmad Samir <a.samirh78@gmail.com>
Date: Thu, 29 Jul 2021 18:45:45 +0200
Subject: [PATCH] Fix MainWindow size when there is no saved size

The very first time a user runs Konsole, where is no konsolerc file in $HOME,
there is no saved size to restore, instead use the sizeHint(), which ideally
will be the size set in the default profile (based on lines/columns setting).


https://invent.kde.org/utilities/kon...bc06c5ab.patch

EDIT: I test the patches and all is fine , tollbars and initial size on first run.
This looks promising, does Konsole indeed open as login shell if you set the command in the profile /bin/bash -l ?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:57 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration