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 appears to be a bit of a change to the normal run of events. PV had updated K3B in 13.1 just because it has gone stable! No bug fix, no security alert, just a version bump.
We have to ask the question where is Pat Volkerding and how can we get him back?
Who says that Slackware is unsurprising. I can just imagine all those system admins going into collective apoplexy as their brains struggle to cope with slackware being bleeding edge.
These are not bleeding-edge, but apparently mature pieces of software. Or was the k3b upgrade possible, because it was only a version bump, with no changes of source code?
If Or was the k3b upgrade possible, because it was only a version bump, with no changes of source code?
Thats inaccurate cause that is the case for the latest development release which Slackware never included.
According to the changelogs k3b was last updated in Slackware on May 6th, while the latest k3b devel release, for which the k3b release announcement is talking about, was released on 16th of June, even after 13.1.
I was just asking a question, not making a statement, but I should have done the research you did myself. Thanks for clearing this up, anyway.
But the more: If it's possible for k3b, what about other stuff?
Is the argument, that for the other programs there are released versions included, while for k3b only a development snapshot was part of Slackware 13.1, that could now, finally, be replaced by a released version?
If K3B finally went stable in 13.1, I'm grateful. K3B in 13.0 was highly unstable. If you set a few options it didn't like it would just crash. Granted it was consistently reproducible and therefore avoidable and it still did the basic job... But still. 13.1 had to come out and couldn't wait around for K3B to be properly released before including it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
