LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   "slackpkg check-updates" only checks for .TXT files? (https://www.linuxquestions.org/questions/slackware-14/slackpkg-check-updates-only-checks-for-txt-files-4175552713/)

Altiris 09-05-2015 03:57 PM

"slackpkg check-updates" only checks for .TXT files?
 
The docs states that the "slackpkg check-updates" command will check for any available updates, which....is somewhat true. If I run that command while some updates have been added by Patrick and team I will get this,
Code:

slackpkg check-updates

News on ChangeLog.txt

  [ Repository              ] [ Status              ]
    slackware                    AVAILABLE UPDATES   
    slackpkgplus                    Up to date       
    restricted                      Up to date       
    alienbob                    AVAILABLE UPDATES   
    multilib                        Up to date

However, if I run "slackpkg update" and then run "slackpkg check-updates" I will get back the "No news is good news" and it will appear as if my system is up to date, however doing "slackpkg upgrade-all" will show that there are available packages to be upgraded. Is this how it is intended to work? To only tell the user of new packages/file available and not per specific program (like many other package manager's on linux)? I am finding it a bit misleading/confusing the way it is now.

yars 09-05-2015 04:04 PM

slackpkg only checks the ChangeLog, but not a installed packages, because that may lead to longer time to checking updates.

Tonus 09-05-2015 04:30 PM

"slackpkg check-updates" only checks for .TXT files?
 
The check-updates command just tells if it worths downloading the changelogs with the update command.

Save bandwidth is a good thing when you have slow or limited data plan.

Alien Bob 09-05-2015 04:37 PM

Quote:

Originally Posted by Altiris (Post 5416386)
The docs states that the "slackpkg check-updates" command will check for any available updates, which....is somewhat true. If I run that command while some updates have been added by Patrick and team I will get this,
Code:

slackpkg check-updates

News on ChangeLog.txt

  [ Repository              ] [ Status              ]
    slackware                    AVAILABLE UPDATES   
    slackpkgplus                    Up to date       
    restricted                      Up to date       
    alienbob                    AVAILABLE UPDATES   
    multilib                        Up to date

However, if I run "slackpkg update" and then run "slackpkg check-updates" I will get back the "No news is good news" and it will appear as if my system is up to date, however doing "slackpkg upgrade-all" will show that there are available packages to be upgraded. Is this how it is intended to work? To only tell the user of new packages/file available and not per specific program (like many other package manager's on linux)? I am finding it a bit misleading/confusing the way it is now.

Look at it like this:

slackpkg downloads repository information from a remote server to your local computer. At any time you can run "slackpkg upgrade somepackage" and slackpkg will use its locally stored cache to find out what version to download. It only contacts the remote server for the package download but does not check for newer files.

The "slackpkg check-updates" on the other hand, compares the state of slackpkg's information on your local computer, with the reality on the remote server and will warn if it detects any remote changes.
After you've noticed that the remote server has updates and you run "slackpkg update" your local slackpkg cached information is identical to the remote server and therefore a second "slackpkg check-updates" will not report anything new.
When you run "slackpkg update" it is your responsibility to also run "slackpkg install-new" and "slackpkg upgrade-all". What else is the purpose of "slackpkg update" if you have no intention of updating?


All times are GMT -5. The time now is 07:04 PM.