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.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
I will see if I can update the 1st post with all the things in this thread, and also list what rworkman has scheduled (please note that packages scheduled by rworkman does not mean it will be updated by PV)
rworkman only makes it easy available for PV to grab if he wants to use it.
I will see if I can update the 1st post with all the things in this thread, and also list what rworkman has scheduled (please note that packages scheduled by rworkman does not mean it will be updated by PV)
rworkman only makes it easy available for PV to grab if he wants to use it.
I'd like to vote for d/ruby. We should have something newer than 1.9.3 as the system Ruby. Lots of projects are starting to need 2.1.x features. I just built 2.2.0p0 (Christmas release) using Pats existing Slackbuild with no changes (well except the version variable). Works fine.
I can state the same being true regarding a clean build and functional Ruby environment for 2.1.x line as well again with the existing build if Pat isn't keen on using a p0 release.
Michael and the contributors have been working hard to improve
the system api docs. I have been working on some of the date-time
issues, mostly in tzset(3). There is still more to do, but it's
significantly improved.
I've also been working on similar changes for the glibc manual,
which is, more or less, parallel documentation. The shear volume
of activity on that project slows progress a little.
I think if and when we get to page 20 we should look at the current package list to the proposal list and see what still is in lue of updates and get a full list up.
Well, there's no "I handle $x list" really. Though there are things that I typically manage and Pat pulls the results from me, everything is ultimately managed by him. For *really* core stuff like init scripts, the only reason I usually make changes is if something else I touched caused problems there (e.g. util-linux upgrade required some fixes there).
That said, yes, the list you quoted is what I had at that time in my pending queue for Pat. I try to keep it up to date as time progresses, but sometimes I miss stuff (and Pat generally catches those when he pulls them into the main repo).
Anyway, the rest of the timedate changes would have to come from Pat. I've got a couple of Slackware servers on darknets, so your changes there would be welcome to me as well.
Anyway, the rest of the timedate changes would have to come from Pat. I've got a couple of Slackware servers on darknets, so your changes there would be welcome to me as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.