[SOLVED] Slackpkg-15.0
by 3rensho from LinuxQuestions.org on (#5DX8W)
Did the upgrade today including the new slackpkg-15.0 and have some questions about how the new slackpkg works. Perhaps I'm a bit dense but the following things make no sense to me -
1) With the previous version I would run slackpkg update and it would cycle thru the sources (I have slackpkg+ installed too) checking for updates. If I ran slackpkg update again it would check and then stop and tell me that there are no new packages and ask do I want to download the package list again. With the new version it simply runs thru the whole list again ignoring the fact that there were no changes since the previous check.
2) I read about the new blacklist syntax and uncommented the lines pertaining to kernel updates since I always build the packages myself. That said, when I run slackpkg upgrade-all it still offers to install kernel-huge-5.10.14-x86_64-1.txz. Is that supposed to happen?
3) I had several SBo packages blacklisted and with the old slackpkg that worked fine. With the new version it still offers to update them even though I have changed the syntax as far as I understand it.
Thanks for un-confusing this old brain.
1) With the previous version I would run slackpkg update and it would cycle thru the sources (I have slackpkg+ installed too) checking for updates. If I ran slackpkg update again it would check and then stop and tell me that there are no new packages and ask do I want to download the package list again. With the new version it simply runs thru the whole list again ignoring the fact that there were no changes since the previous check.
2) I read about the new blacklist syntax and uncommented the lines pertaining to kernel updates since I always build the packages myself. That said, when I run slackpkg upgrade-all it still offers to install kernel-huge-5.10.14-x86_64-1.txz. Is that supposed to happen?
3) I had several SBo packages blacklisted and with the old slackpkg that worked fine. With the new version it still offers to update them even though I have changed the syntax as far as I understand it.
Thanks for un-confusing this old brain.