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.
A two to three year development cycle is sane these days with complex operating systems.
One reason many of us use Slackware is Patrick takes his time producing mother-f-cking stable systems. Most of us are not interested in rapid release or being members of some PR click-bait kernel-of-the-week update club. Update now!
Anybody needing or wanting the latest and greatest (ha!) software probably should use Current or another distro.
It's uncomfortable to plan for a derivative of or for third party projects related to a distribution that doesn't publish its plan, if it has one. But that's life.
Last edited by Didier Spaier; 01-22-2024 at 04:05 PM.
It's uncomfortable to plan for a derivative of or for third party projects related to a distribution that doesn't publish its plan, if it has one. But that's life.
You know, I spent the whole day until late tonight, doing a lot of crappy stuff on servers to get around problems
For what ?
"Because the production starts tomorrow at 7AM"
That kind of logic has no place anywhere and least of all here
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,154
Rep:
Quote:
Originally Posted by lostintime
.....mother-f-cking....
Really!?
It would appear that all we have accomplished over the last forty to fifty years is to drag the entire society down to the lowest common denominator.
Really!?
It would appear that all we have accomplished over the last forty to fifty years is to drag the entire society down to the lowest common denominator.
Sorry! Old man moment. Sometimes I forget I'm in public and some people dislike colorful language. At least I wasn't in line at the DMV passing gas.
My removed_packages and removed_scripts only date back to 2018-06-22. (The oldest files in packages and scripts are 2009-06-01).
Code:
Thu Jun 21 22:58:42 UTC 2018
a/pkgtools-15.0-noarch-20.txz: Rebuilt.
Move pkgtools database to /var/lib/pkgtools/.
Move removed logs to /var/log/pkgtools/.
I noticed at that time that removed_packages and removed_scripts were cleared but I thought they were considered not important enough to be kept. But now I read the pkgtools install script and saw that they were meant to be saved. There are two lines like this:
The contents of the old removed_packages and removed_scripts directories were not moved because the command line was too long, and stderr was devnulled.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
