Why customise url when the rest of the file does not customise it, and the only purpose of download-base is to automatically build that URL to begin with ?
Where is the checksum verified ? This section is not present in buildout.hash.cfg.
What is the expected filename once downloaded ? The other sections specify that name by declaring homonymous sections in buildout.hash.cfg.
Why customise `url` when the rest of the file does not customise it, and the only purpose of `download-base` is to automatically build that URL to begin with ?
Where is the checksum verified ? This section is not present in `buildout.hash.cfg`.
What is the expected filename once downloaded ? The other sections specify that name by declaring homonymous sections in `buildout.hash.cfg`.
Also, please do not use a subfolder for a single template when the rest of the SR is careful to not use a subfolder.
The reason of this being precisely to support buildout.hash.cfg in a portable manner.
Also, please do not use a subfolder for a single template when the rest of the SR is careful to *not* use a subfolder.
The reason of this being precisely to support `buildout.hash.cfg` in a portable manner.