Open weaverba137 opened 2 years ago
This sounds good. I suggest wrapping that in a script, perhaps kept in basis_templates svn rather than desisim, for tagging + checksumming basis_templates correctly. We could use that to make a new tag just to cleanup the checksum situation for the most recent tag.
@moustakas, @sbailey, are there ever going to be new tags of basis_templates
?
I think it's not inconceivable that we revisit the desisim
infrastructure and develop new basis templates going into desi-2 and beyond, so I wouldn't count it out.
Prior to basis_templates/v3.0, tags contained a checksum file. However more recent tags do not contain this file. Uploading and downloading very large binary files with svn is always a bit tricky, so the checksum file helps protect against corruption.
Here are some non-binding suggestions:
sha256sum
and call it, e.g.,basis_templates_v3.3.sha256sum
. That is, include the tag in the name.basis_templates/trunk
for tagging, including creating the checksum file, modifyingbasis_templates_trunk.sha256sum
as needed.basis_templates_trunk.sha256sum
.Here's some code that illustrates this: