On 20/07/2020 12:30, Ralph Corderoy wrote: > > If the tar-file download doesn't include the revision in its filename > and the directory it unpacks then I'd either post-process it to do that > or stop using the web download and do a proper ‘release’ target in the > software's makefile. Then when you want a release to ship you > > make REV=12345678ab release > > and it creates a ‘wmt-12345678ab.tar.lzip’ or similar which is a > check-out of that revision from the public repo into directory > ‘wmt-12345678ab’, all tar'd up. > > You can ship those tar files about, unpack them, and then alter a ‘wmt’ > symbolic link to move between which version will be used, allowing for > easy downgrade on a machine with no Internet. > > Code can inspect the ‘real’ path to its location to determine its > version for logging, etc. > Sadly, seeing as this is Python software, we don't have a makefile. I know there are a variety of ways to solve this going forwards, including even just noting what the commit was at the time of deployment on our forum or something like that, but this is more about how to solve the present issue. Sadly, I think the tarball might just not include any revision details.
Whatever we do, it needs to be as simple as possible to ease the life of future maintainers - things like Makefiles and symlinks are probably not ideal, but thanks for the ideas :) Hamish
signature.asc
Description: OpenPGP digital signature
-- Next meeting: Online, Jitsi, Tuesday, 2020-08-04 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
