Tracking rebuilt stock 15.0 packages with slackpkg(plus)
by chris.willing from LinuxQuestions.org on (#5GRGS)
With 15.0 in beta, it's becoming clear that some of my pet requests won't be accommodated and that I will have to rebuild some of the stock packages myself. I don't have a particular problem with that but I'd like to streamline the way future upgrades are handled. I've previously maintained a local server with private updates and additional packages to keep a lab of about a dozen machines up to date using slapt-get but more recently moved to slackpkg & slackpkg+. What is missing though is a way to know when a base package has been updated so that I can know that I need to rebuild/update my private version.
Take, for example, ffmpeg which is currently at version 4.4. I can rebuild it with whatever additional options I want and put the result onto my private server which I have given higher priority than a standard slackware mirror. That much is easy. However when the stock version has been updated to, say, version 4.5, it will be silently ignored since the private server (with only version 4.4) has priority. I should therefore update my private version - that's understood - but how can I know I need to do that?
Is there a way that slackpkg(plus), or even slapt-get, can be verbose enough to let me know that a lower priority server has a higher package version than the higher priority server?
chris


Take, for example, ffmpeg which is currently at version 4.4. I can rebuild it with whatever additional options I want and put the result onto my private server which I have given higher priority than a standard slackware mirror. That much is easy. However when the stock version has been updated to, say, version 4.5, it will be silently ignored since the private server (with only version 4.4) has priority. I should therefore update my private version - that's understood - but how can I know I need to do that?
Is there a way that slackpkg(plus), or even slapt-get, can be verbose enough to let me know that a lower priority server has a higher package version than the higher priority server?
chris