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.
Now that the latest batch of changes is public (and it's a *big* batch), look and see what's still missing/untouched and let us know. For things that aren't simple version bumps, some rationale would be good.
I'm already looking at new Xorg stuff, so don't mention that.
I've also got some slightly intrusive changes queued for usbutils and pciutils along with sg3_utis, sdparm, keyutils, ulogd, libsecret, tar, and manpages, along with a few other very minor things.
urwid and wicd still fail some tests here wrt functionality; if anyone wants to mess with that and pass it along to me or Pat, feel free (and good luck). New NM has the nmtui curses client now, so wicd is a wash as far as I'm concerned.
I've also got new polkit and polkit-gnome queued, and while they seem fine now, I had some initial issues with them; if anyone's interested in testing that out, I can pass along the relevant build stuff.
Addendum 20150422: We already know that PAM is desired by some and not by others. This is not a place to discuss it or give pros/cons of either, as those are pretty much known too. Whether it's ever been or is currently under consideration is not my place to say, but I will point out that every time there's a new flame fest about it, none of us want to touch it again for a while. Let that be a point of education.
Last edited by rworkman; 04-22-2015 at 01:40 PM.
Reason: PAM
Now that the latest batch of changes is public (and it's a *big* batch), look and see what's still missing/untouched and let us know. For things that aren't simple version bumps, some rationale would be good.
Great update!
What's missing? For me, Tcl/Tk 8.6.1 to 8.6.4 perhaps? I'm currently learning this great language. I'm not sure whether or not the version bump would break something else.
great thing, glad to see that again current hat an actual C/C++ development environment
but ruby version needs to be replaced
Quote:
Support for Ruby 1.9.3 has ended
Posted by Olivier Lacan on 23 Feb 2015
As of today, all support for Ruby 1.9.3 has ended. Bug and security fixes from more recent Ruby versions will no longer be backported to 1.9.3.
This end of life was announced over a year ago.
We highly recommend that you upgrade to Ruby 2.0.0 or above as soon as possible. Please contact us if you’d like to continue maintaining the 1.9.3 branch for some reason you can’t upgrade
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,646
Rep:
larryhaja suggested a sip update in that other thread: http://www.linuxquestions.org/questi...ml#post5309597 and I add my +1
AFAIR I needed an update some time ago to install PyQt for python3 but cannot say if it might break other stuff.
I wonder, since KDE desktop indexer switched to baloo, if there are not some packages that should have some nepomuk remove in the change log.
but it seems nepomuk core got an update and there are no removes, are these not exlusive?
Just a heads up: audacious-3.6.1 now has libaudclient off a separate package (see http://audacious-media-player.org/?page=2). Found it because I had to rebuild conky off SBo and it won't build due to it having a default `--enable-audacious` in the SlackBuild script.
Just a heads up: audacious-3.6.1 now has libaudclient off a separate package (see http://audacious-media-player.org/?page=2). Found it because I had to rebuild conky off SBo and it won't build due to it having a default `--enable-audacious` in the SlackBuild script.
With it no longer being developed, I don't think it's a good candidate for inclusion in Slackware, especially since I'm not aware of anything in the core actually requiring it. For things like conky it should be enough to have it on SBo, eventually.
I would not want to see Python 3 included until a) every Python file in the distribution runs with Python 3 and b) every library in the distribution that links against Python is linked against Python 3.
Don't really want to see Slackware shipping one Python interpreter for actual use (because it's what the distribution's packages and libraries have been built for) and another one that doesn't have any distribution support but is newer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.