On 20/07/2020 13:45, Terry Coles wrote: > On Monday, 20 July 2020 13:35:19 BST Hamish McIntyre-Bhatty wrote: >> 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 :) > Presumably, when the makefile described by Ralph processes this, it creates > this zip through some kind of script. > > Couldn't we just create a 'Release' script that works on a text file > containing > the full list of files in the system (as a makefile does) fetches them from > GitLab, zips them up and names the resulting archive with the Revision Number? > > In other words a makefile, but without the compilation stage. > > Have I missed something? > No, I think we absolutely could do that, and it would be a good solution, though perhaps a little tricky for future maintainers. If you think we should do that then I'm happy to write us such a script.
However, I was looking to a solution to the existing problem of not knowing exactly what revision/commit we have deployed :) 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
