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.
Version 1.0rc2 - 21/Oct/2013
- Looks like we get a slackpkg+ 1.0 release candidate 2... but things are
pretty much nailed down at this point. Please test and report any last
- Updated some repository to 14.1
slackpkg TRY to detect if the package is newer of the installed package (may fail) and deselect it by default if it is older.
detection may fail on packages as 1.2 vs. 1.12 ( 2 is alphabetically after 12; that problem may be partially solved in a future review).
I may decide to disallow the check if it is from the official slackware repository.
Please do not add version comparison checks to the script, or at least leave it disabled by default when you add this.
Your change to the script goes against the way Slackware looks at package upgrades: Slackware does not care if a version is older or newer. That is a strength, not a weakness. Just like the lack of dependency checks is a strength, not a weakness.
Also you will not be able to be 100% accurate on version checks.
Suppose a developer releases a beta version of his software and calls the version "1.0b". Then he releases his stable release and calls it "1.0". Your algorithm would incorrectly consider "1.0b" as a higher version than "1.0".
The user can see the version in the last line of screen.
Insert the version inline enlarge the dialog out-of-screen (you must put also the build version), and the user must to check manually all packages listed.
Please do not add version comparison checks to the script, or at least leave it disabled by default when you add this.
I will add an entry in slackpkgplus.conf
Quote:
Your change to the script goes against the way Slackware looks at package upgrades: Slackware does not care if a version is older or newer. That is a strength, not a weakness. Just like the lack of dependency checks is a strength, not a weakness.
Quote:
Originally Posted by zerouno
I may decide to disallow the check if it is from the official slackware repository.
yes, some slackware upgrades are 'downgrade'
Quote:
Also you will not be able to be 100% accurate on version checks.
I will try to increase the accuratation, but I may add an entry in slackpkgplus.conf that does not de-check by default then package if it is older.
Quote:
Suppose a developer releases a beta version of his software and calls the version "1.0b". Then he releases his stable release and calls it "1.0". Your algorithm would incorrectly consider "1.0b" as a higher version than "1.0".
yes, is better in a future beta and/or in a development branch. The rc is freezed.
I was thinking for a method, even without the autodeselect and only for third-party repositories, to show the user quickly if a third-party package is newer or older without having to compare one by one, and maybe leave him choose to install or not.
In practice I have, in my system, a series of packages that are newer than those found in the configured repositories, and each upgrade-all I get that packages listed.
I do not blacklist them because I would have no more any update notifications, but in the meantime I have to deselect them every time.
And when there are big updates (today I've updated ktown) it can miss to deselect one, so start a downgrade.
But evidently the functionality should be thought best to reduce the intrusiveness and maintain the philosophy of slackware.
@zerouno: slackpkg+ is just perfect as is. As far as I'm concerned, you should be given a "Handy Slackware Tool Of The Year Award" for it. Anyway, I've added a big THANK YOU note in my repository (http://www.microlinux.fr/slackware/README.txt).
The only thing that's left to do is correct a few typos, but that's all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.