On 12Apr2021 19:11, Rich Shepard <rshep...@appl-ecosys.com> wrote: >On Tue, 13 Apr 2021, Cameron Simpson wrote: >>Alternatively, and now that I think about it, more simply: _if_ the >>package files can be sorted by version, then all you need to do is read a >>sorted listing and note that latest fil for a particular package. If you >>need another one, it should be newer and you can remove the "known" >>package file, and update your record that to the new one. > >The problem is not that simple. Sometimes the package maintainer upgrades >the package for the same version number so there could be abc-1.0_1_SBo.tgz >and abc-1.0_2_SBo.tgz. The more involved route will be taken.
If that _1, _2 thing is like RedHat's -1, -2 suffixes for later releases of the same source package version, you could just include that in the version string. Looks like it counts up. Cheers, Cameron Simpson <c...@cskk.id.au> -- https://mail.python.org/mailman/listinfo/python-list
