Alternative update approach to slackpkg - request for testing/feedback
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.
- eventually, to put also a blacklist for slackscan
It could be interesting :
- to put /var/lib/slackpkg by default in the conf
- and to automatically retrieve the uncommented mirror in /etc/slackpkg/mirrors
this way, even with an unmodified configuration file, the slackscan would work
- to display the package names (with a special mention) instead of "not available", even if they are external slackbuilds
Thanks for taking the time to have a look and to comment.
Quote:
Originally Posted by marav
- eventually, to put also a blacklist for slackscan
I intentionally kept slackscan light on features as per the UNIX philosophy:
Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.
slackscan's "one thing" is to look what package files are available in its configured locations and then generate lists of packages to be added, updated or removed.
If you want to do a blacklisting then 'grep -v' will serve nicely.
For example, if I wanted to update/install everything except stuff in a blacklist and remove any removed files except stuff from SBo, then I could:
This is pretty much the same as an update, install-new, upgrade-all, clean-system run in slackpkg.
The above is pretty much what early versions of my 'slackup' script did before I expanded its feature set and made it output a command stream instead. Doing the above is likely a little unwieldy for the average user, which is why I wrote slackup with all those nice features like blacklists and filtering. all behind a more accessible command-line interface.
Quote:
Originally Posted by marav
It could be interesting :
- to put /var/lib/slackpkg by default in the conf
- and to automatically retrieve the uncommented mirror in /etc/slackpkg/mirrors
this way, even with an unmodified configuration file, the slackscan would work
Actually, slackscan might make a better back-end for slackpkg than the other way around.
Quote:
Originally Posted by marav
- to display the package names (with a special mention) instead of "not available", even if they are external slackbuilds
I'm not really sure what you mean here. The "not-available" stuff you see mentioned within the script itself is just used internally, the user will never see that. slackscan will output a list of packages whose package files have been removed to the file specified by the -r option.
For example, if I temporarily remove my hw-accel/ dir from my package locations to simulate some removals, it will look like this:
I'm not really sure what you mean here. The "not-available" stuff you see mentioned within the script itself is just used internally, the user will never see that. slackscan will output a list of packages whose package files have been removed to the file specified by the -r option.
For example, if I temporarily remove my hw-accel/ dir from my package locations to simulate some removals, it will look like this:
You can't just comment out those joins like that, they're essential for the way slackscan works and it will corrupt slackscan's internal database table.
Are you saying that happened before you commented out those joins?
If so, that shouldn't happen. Please can you post your default.conf so I can try and debug. Also what $LANG are you running.
Are you saying that happened before you commented out those joins?
If so, that shouldn't happen. Please can you post your default.conf so I can try and debug. Also what $LANG are you running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.