LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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 06-16-2020, 05:32 AM   #5221
saxa
Senior Member
 
Registered: Aug 2004
Location: Nova Gorica, Salvador
Distribution: Slackware
Posts: 1,205

Rep: Reputation: 295Reputation: 295Reputation: 295

Quote:
Originally Posted by mats_b_tegner View Post
I've been able to compile pidgin 2.14.1 now by enabling voice support. This requires farstream which is available on SBo.
Yes without --disable-vv should work well and manager.h has the definition of that structure in it, embraced by the #ifdef DIS_VV
which takes that definition out if you use --disable-vv. Anyway glad you made it go.
 
1 members found this post helpful.
Old 06-16-2020, 09:43 AM   #5222
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 burdi01 View Post
Who said so? What did I miss?
"Expected". Pat has said a few times that Plasma5 is something he's looking at.
 
1 members found this post helpful.
Old 06-16-2020, 09:54 AM   #5223
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware Current64, PartedMagic, Xubuntu
Posts: 465

Rep: Reputation: 114Reputation: 114
I was responding to the "soon", not to the "expected".
 
Old 06-16-2020, 09:56 AM   #5224
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,465

Rep: Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258
Quote:
Originally Posted by bassmadrigal View Post
"Expected". Pat has said a few times that Plasma5 is something he's looking at.
If instantly I had been married to every lady when the young me looked at their "features" most likely today half of the young ones from my own city had been called me "Dad" ...

Just saying - "looking" is a completely different thing from "engagement".

Last edited by LuckyCyborg; 06-16-2020 at 09:58 AM.
 
Old 06-16-2020, 10:23 AM   #5225
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 2,011

Rep: Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619
Any reason why we are stuck on eigen3 version 3.2.10 from 2016? 3.3.x has built-in CMake support, for one advantage.
 
1 members found this post helpful.
Old 06-16-2020, 10:52 AM   #5226
ziprun
Member
 
Registered: Apr 2018
Posts: 105

Rep: Reputation: Disabled
Can we please have OpenJDK 11 added to Slackware 15.0? Any of the previous licensing issues has been completely resolved.
 
4 members found this post helpful.
Old 06-16-2020, 11:56 AM   #5227
tux2x
LQ Newbie
 
Registered: Jun 2020
Posts: 11

Rep: Reputation: Disabled
I tried to search for slackware 15 release but the search function doesn't function
Does anyone "know" if 15 will be released soon?
 
Old 06-16-2020, 12:22 PM   #5228
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 burdi01 View Post
I was responding to the "soon", not to the "expected".
It was long expected that PAM was the hold up in getting Plasma5 into the system. "Expected" and "soon" are all speculative. Until there's an official announcement, it's just guessing.

Quote:
Originally Posted by LuckyCyborg View Post
If instantly I had been married to every lady when the young me looked at their "features" most likely today half of the young ones from my own city had been called me "Dad" ...

Just saying - "looking" is a completely different thing from "engagement".
There are a lot of signs pointing to Plasma5 being added "soon", even in the changelog:

Code:
l/PyQt5-5.13.2-x86_64-2.txz:  Rebuilt.
  Added python2 modules, as Plasma 5 needs these for now.
  We will eliminate python2 as soon as possible, but not sooner.
Code:
Wed Feb 12 05:05:50 UTC 2020
Hey folks! PAM has finally landed in /testing. Some here wanted it to go
right into the main tree immediately, and in a more normal development cycle
I'd have been inclined to agree (it is -current, after all). But it's
probably better for it to appear in /testing first, to make sure we didn't
miss any bugs and also to serve as a warning shot that we'll be shaking up
the tree pretty good over the next few weeks. I'd like to see this merged
into the main tree in a day or two, so any testing is greatly appreciated.
Switching to the PAM packages (or reverting from them) is as easy as
installing all of them with upgradepkg --install-new, and if reverting then
remove the three leftover _pam packages. After reverting, a bit of residue
will remain in /etc/pam.d/ and /etc/security/ which can either be manually
deleted or simply ignored. While there are many more features available in
PAM compared with plain shadow, out of the box about the only noticable
change is the use of cracklib and libpwquality to check the quality of a
user-supplied password. Hopefully having PAM and krb5 will get us on track
to having proper Active Directory integration as well as using code paths
that are likely better audited these days. The attack surface *might* be
bigger, but it's also a lot better scrutinized.
Thanks to Robby Workman and Vincent Batts who did most of the initial heavy
lifting on the core PAM packages as a side project for many years. Thanks
also to Phantom X whose PAM related SlackBuilds were a valuable reference.
And thanks as well to ivandi - I learned a lot from the SlackMATE build
scripts and was even occasionally thankful for the amusing ways you would
kick my ass on LQ. ;-) You're more than welcome to let us know where we've
messed up this time.
The binutils and glibc packages in /testing were removed and are off the
table for now. I'm not seeing much upside to heading down that rabbit hole
at the moment. Next we need to be looking at Xfce 4.14 and Plasma 5.18 LTS
and some other things that have been held back since KDE4 couldn't use them.
This is when PAM was added to testing/. Now that it's been pushed to prime, I imagine all the testing is happening on their end and dealing with all the possible changes that might come with it (elogind, wayland, upower, and who knows what else).

Quote:
Originally Posted by tux2x View Post
I tried to search for slackware 15 release but the search function doesn't function
Does anyone "know" if 15 will be released soon?
Pat doesn't even know when 15.0 will be released. Slackware firmly follows the "release it when it's ready" philosophy. Until we start seeing beta or release candidates, it could be anything from a few months or a few years. Once we start seeing betas or release candidates, the stable release will hopefully be no more than a few months after that.
 
2 members found this post helpful.
Old 06-16-2020, 10:38 PM   #5229
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,949

Rep: Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531
Quote:
Originally Posted by bassmadrigal View Post
Until we start seeing beta or release candidates, it could be anything from a few months or a few years. Once we start seeing betas or release candidates, the stable release will hopefully be no more than a few months after that.
Just thought I'd toss my thoughts on -current out there.

I used to consider the -current branch to be in the beta phase of testing, simply because it rarely breaks. After a bit of research (e.g., ChangeLog.txt's).

I now consider the current branch to be in the alpha phase. Reason? Well Patrick references beta release in several of the ChangeLog.txt files. That basically says it all. Before beta, comes alpha. History of ChangeLog.txt entries show that we could go beta before a release candidate, or we could skip beta and go straight to a release candidate, or we could just jump right to a release. It is really all up to what Patrick decides.

So in summary, at least in my opinion, anyone who uses Slacware-current or Slackware64-current is an alpha tester. That includes me of course. Happy testing!

Last edited by chrisretusn; 06-16-2020 at 10:48 PM.
 
Old 06-17-2020, 03:14 AM   #5230
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by chrisretusn View Post
I now consider the current branch to be in the alpha phase. Reason? Well Patrick references beta release in several of the ChangeLog.txt files.
In my understanding, "beta release" is an oxymoron: a software is in one state or the other, as stated by its authors.

I assume that you allude to some entries in a ChangeLog that mention a git commit, like:
l/libimobiledevice-20200615_4791a82-x86_64-1.txz: Upgraded.
or
ap/usbmuxd-20200615_3daa1e9-x86_64-1.txz

If you have a look at these commits, you will realize that the first one is just a post-release version bump: nothing changed in the code since version 1.3.0.
The second one is also just a post release version bump with no change in the code.

So there is no rationale to tag these software "beta".

Also, it's possible that a coder using a git repository never makes an official release. This doesn't mean that the software is not ready for use.

Further, I don't see anything wrong shipping a software pulled from git master, as long you trust the author, if that brings a major bug fix or a long awaited feature. I just did that less than two days ago, cf. this ChangeLog. In one case I even patched from a not-yet-commited pull request

So no, I don't see a rationale to label people using Slackware current "alpha" testers. Let's just name them testers.

Last edited by Didier Spaier; 06-17-2020 at 04:15 AM. Reason: s/a code/a coder/ s/call/name/
 
1 members found this post helpful.
Old 06-17-2020, 04:50 AM   #5231
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current, Ubuntu (servers)/Windows 11 (workstations)
Posts: 588

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Quote:
Originally Posted by Didier Spaier View Post
So no, I don't see a rationale to label people using Slackware current "alpha" testers. Let's just name them testers.
Good point!
Slackware64-current is quite stable, not even PAM has destabilized it.
 
Old 06-17-2020, 05:26 AM   #5232
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,949

Rep: Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531
Quote:
Originally Posted by Didier Spaier View Post
In my understanding, "beta release" is an oxymoron: a software is in one state or the other, as stated by its authors.

I assume that you allude to some entries in a ChangeLog that mention a git commit, like:
l/libimobiledevice-20200615_4791a82-x86_64-1.txz: Upgraded.
or
ap/usbmuxd-20200615_3daa1e9-x86_64-1.txz
No actually I referred to actual ChangeLog.txt entries. Did you miss the:
Quote:
Originally Posted by chrisretusn View Post
After a bit of research (e.g., ChangeLog.txt's).
Code:
+--------------------------+
Fri Aug 30 14:19:08 PDT 2002
We're happy to announce the initial Slackware-9.0-beta based on gcc-3.2. :-)
Please test it and report any bugs that you find.

+--------------------------+
Fri Sep 12 00:47:02 PDT 2003
Here comes Slackware 9.1 beta-1!  (things are looking good, so expect
  a very short beta cycle. :-)  ZipSlack still to come.

+--------------------------+
Wed Sep 17 02:00:02 PDT 2003
Slackware 9.1-beta2 is ready for testing...

+--------------------------+
Sat Jan 22 18:12:37 PST 2005
"Goes to show, you don't ever know"

Hi folks!
  I'm going to call this Slackware 10.1 beta 1, because we're at a state
where things are relatively stable.

+--------------------------+
Tue Aug  2 15:34:18 PDT 2005
Hi folks,
I think it's time to consider this to be mostly frozen and concentrate on
beta testing in preparation for the Slackware 10.2 release, so there won't
be too many more upgrades and additions. 

+--------------------------+
Sat Mar 17 19:14:35 CDT 2007
  Happy St. Patrick's Day!  :-)
  This is more-or-less stable (functionally), but there's still a lot of
  package splitting and other rearranging and adding to be done, but it's
  time for the Slackware community to see how far we've gotten.  If the
  luck o' the Irish is with us, it'll be a fairly short alpha/beta/rc
  period from here.  Well, have fun!

+--------------------------+
Thu May  6 21:02:02 UTC 2010
Hi folks!  We have some pretty big changes today, with an update to the latest
KDE SC 4.4.3, and the addition of support for ConsoleKit and PolicyKit which
have been enhanced to use shadow authentication.  Thanks to Andrew Psaltis for
doing some great work on polkit-1, and to Robby Workman for spending months
following the sometimes random developments coming from the CK/PK camp.  :-)
Thanks to Eric Hameleers for leading the KDE 4.4.x Slackware development and
handling the out-of-tree testing through http://alien.slackbook.org/blog/.
And with that, we're calling this Slackware 13.1 BETA1.  A stable release
should be just around the corner...

+--------------------------+
Sun Jul 22 22:38:36 UTC 2012
Howdy!  Lots of shiny stuff here, including the long awaited Xfce 4.10!
Thanks to Robby Workman for the initial set of build scripts, and lots
of testing (plus some very helpful notes about things such as the proper
build order).  I'm calling this a beta (finally!), and it's really very
close to what we expect to release.  Test away.

+--------------------------+
Tue Aug  6 05:23:34 UTC 2013
Looks like 3.10.x got LTS status, but more importantly fixes the power issue
on resume with some Intel machines.  So, we're bumping the kernel to 3.10.5,
and will stick with that series for the release.  A few more things to look at
before calling this a beta, but it's pretty close.  Enjoy!

+--------------------------+
Wed Sep 18 02:56:19 UTC 2013
Hey folks, I'm calling this a beta!  Really, it's been better than beta
quality for a while.  There will probably still be a few more updates
here and there (and certainly updates to the docs).  Enjoy, and please test.

+--------------------------+
Tue Apr 21 23:44:00 UTC 2015
Greetings!  It has indeed been far too long.  I apologize for the absence
of updates lately, but we've been using the time to get some good work done.
This is not a beta (probably not even an alpha release yet), but it is also
not a drill.  ;-) 

Sat Nov 14 21:35:57 UTC 2015
Please enjoy "almost a beta."  Sorry we missed Friday the 13th this time.

+--------------------------+
Wed Jan 13 00:01:23 UTC 2016
Hey folks, happy new year!
After upgrading to BlueZ 5 recently, everything seemed to be working great,
but then it was pointed out that Bluetooth audio was no longer working.
The reason was that the newer BlueZ branch had dropped ALSA support and now
required PulseAudio.  So with some trepidation, we began investigating adding
PulseAudio to Slackware.  Going back to BlueZ 4 wasn't an option with various
dependent projects either having dropped support for it, or considering doing
so.  After several iterations here refining the foundation packages and
recompiling and tweaking other packages to use PulseAudio, it's working well
and you'll likely not notice much of a change.  But if you're using Bluetooth
audio, or needing to direct audio through HDMI, you'll probably find it a lot
easier to accomplish that.
Best of all, we're finally a modern, relevant Linux distro!  ;-)
Thanks to Mario Preksavec, Heinz Wiesinger, and Robby Workman for a lot of
help and testing.  Bug reports, complaints, and threats can go to me.
Also, enjoy a shiny new LTS 4.4.0 kernel and consider this 14.2 beta 1.

+--------------------------+
Wed Feb  3 22:39:25 UTC 2016
Welcome to Slackware 14.2 beta 2.  Getting closer.  :-)

Quote:
Originally Posted by Didier Spaier View Post
So no, I don't see a rationale to label people using Slackware current "alpha" testers. Let's just name them testers.
I do see the rationale, I standby my above post.

Last edited by chrisretusn; 06-17-2020 at 05:36 AM.
 
Old 06-17-2020, 08:18 AM   #5233
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 2,192

Rep: Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987
We need a statistician to compile all of this, and to deduce the output of the next version
 
1 members found this post helpful.
Old 06-18-2020, 01:05 AM   #5234
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 194

Rep: Reputation: Disabled
BIND 9.16.4
https://www.isc.org/download/
 
Old 06-18-2020, 01:24 AM   #5235
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 946

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Quote:
Originally Posted by saxa View Post
I am sorry, this one is the working one. The previous one still produced an empty nspr-confg.

Code:
--- mozilla-nss.SlackBuild.orig	2020-06-12 11:46:55.530795184 -0300
+++ mozilla-nss.SlackBuild	2020-06-12 12:03:54.131748256 -0300
@@ -28,7 +28,7 @@
 SRCNAM=nss
 VERSION=${VERSION:-3.54}
 NSPR=${NSPR:-4.26}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 
 # Automatically determine the architecture we're building on:
 MARCH=$( uname -m )
@@ -68,7 +68,7 @@
 TMP=${TMP:-/tmp}
 PKG=$TMP/package-$PKGNAM
 
-NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}
+NUMJOBS=${NUMJOBS:-" -j $(expr $(nproc) + 1) "}
 
 rm -rf $PKG
 mkdir -p $TMP $PKG
@@ -119,7 +119,7 @@
 cd -
 
 # Install nspr-config:
-cat nspr/$(uname -s)*/config/nspr-config | sed -e "s,prefix=/usr/local,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
+cat nspr/Release/config/nspr-config | sed -e "s,^prefix=.*$,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
 chmod 755 $PKG/usr/bin/nspr-config
 
 # Install nss-config:
Can somebody test and confirm this one works as expected? On my machine, it worked ok.
This works and is still needed on the latest mozilla-nss-3.54-x86_64-1 package which still has an empty nspr-config file.

Last edited by mats_b_tegner; 06-29-2020 at 05:03 AM.
 
1 members found this post helpful.
  


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 07:31 PM.

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