8.2% of the packages in "current" are already outdated
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.
"Note that sum of columns does not need to match total count, as there may be packages with different status for a single project in a repository. Percentages are also calculated differently."
Not an excellent site.
If this is the most useful thing you have to say, better you stick with Debian.
"Note that sum of columns does not need to match total count, as there may be packages with different status for a single project in a repository. Percentages are also calculated differently."
Not an excellent site.
If this is the most useful thing you have to say, better you stick with Debian.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 454
Rep:
I'm going to go out on a limb here and guess that you've been using Linux for a good long while... long enough to know that having every single package at the latest version is basically impossible due to compatibility issues. Is this really the best troll post you can come up with?
I disagree, the term Current fits. FreeBSD uses the term Current for their development branch too.
What are the odds that an account with the same character attributes as the account that got banned shows up after 7-8 years of no activity to engage in the same behavior as the account that was banned?
I disagree, the term Current fits. FreeBSD uses the term Current for their development branch too.
These are not similar. Slackware packages other people's software.
FreeBSD has its own kernel and base system (to which "current" refers).
Quote:
What are the odds that an account with the same character attributes as the account that got banned shows up after 7-8 years of no activity to engage in the same behavior as the account that was banned?
"Note that sum of columns does not need to match total count, as there may be packages with different status for a single project in a repository. Percentages are also calculated differently."
Not an excellent site.
If this is the most useful thing you have to say, better you stick with Debian.
I reported this post. Let's see if the mod does anything.
But your point is absolutely absent. You are angry that the same package can be listed as "outdated" and "problematic" at the same time? Good one.
What does that have to do with me? I'm not even religious. Religious LARPing is actually a Slackware users' thing.
It was unintentional "religious LARPing" via a Freudian slip which made it funny. The person would engage in different personas. They'd be a dad, a kid, and ... . The end result was a ban each time. Then their next incarnation soon follows the ban of the last one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
8.2% of the packages in "current" are already outdated
