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.
xorg-xserver is now at version 1.18.0 but it will require the latest drivers and some work-arounds for existing drivers.
xf86-video-ati-7.6.1 should work, nouveau's latest git should work, fbdev might need a rebuild against xorg-xserver-1.18.0, but the xf86-video-intel might need a small fix to get it working:
I have seen a few mentions in this thread of the newest gcc 5.2 and I can see from the gcc release dates, and the inclusion of 4.9.3 into the Slackware tree in August, that a choice has perhaps been made for 4.9.3 to be in the next Slackware release:
GCC 5.2 released [2015-07-16]
GCC 4.9.3 released [2015-06-26]
Would the Slackware team consider going with 5.2 considering that the next release of Slackware (after 14.2) might not be until sometime in 2017? I am not completely clear on exactly how 'bleeding edge' gcc 5.2 might be I will admit...
Would the Slackware team consider going with 5.2 considering that the next release of Slackware (after 14.2) might not be until sometime in 2017? I am not completely clear on exactly how 'bleeding edge' gcc 5.2 might be I will admit...
I have no insider information, but my outsider information indicates "not a cat in hell's chance". gcc-5 has a new ABI for C++ and it's a bloodbath.
I was aware of the tendency of vlc developers to be perhaps a little difficult and for the most part I have put this down to them being volunteers with many other demands on their plates. But I confess recent posts by developers (as well as the ongoing tearing of video display in vlc, not present in MPlayer) have led me to consider retreating to my old friend MPlayer and sidelining vlc.
I teach Yoga and lead a Yogic lifestyle and I have been taught that it is sometimes a good strategy to not be associated with negative and angry people... Let the developers of vlc beware .
Q. Assuming that it takes 1.01 day to integrate an upgraded package to Slackware-current, that one upgrade is requested every day and that the Slackware team fulfills all requests, when will Slackware-14.2 be released?
A. Never.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Rep:
Quote:
Originally Posted by Didier Spaier
Q. Assuming that it takes 1.01 day to integrate an upgraded package to Slackware-current, that one upgrade is requested every day and that the Slackware team fulfills all requests, when will Slackware-14.2 be released?
A. Never.
After two years since the last release, what difference does it make? (He said, tongue in cheek )
But I confess recent posts by developers (as well as the ongoing tearing of video display in vlc, not present in MPlayer) have led me to consider retreating to my old friend MPlayer and sidelining vlc.
In my Opinion, mpv is the most obvious candidate to replace/update Mplayer to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.