On Mon, 2018-03-05 at 19:21 +0100, Eduard Braun wrote:
Maybe we can (in the above scenario) construct the information from uploaded filenames?
E.g. for a file called "inkscape-0.92.3pre0.tar.bz2" we immediately know it's version 0.92.3pre0 and it's a source tarball. For binary release we could come up with names like "inkscape-0.92.3pre0-win-x86.exe" telling us it's a release for Windows, i686 architecture, exe installer format. Other metadata (license / authors) should be the same for all Inkscape packages. Checksums/signatures could be pulled in from *.md5/*.sig files of the same name, e.g. inkscape-0.92.3pre0-win-x86.exe.md5.
If it's not straightforward to implement that's OK, though... releases don't happen every day, so at least personally I always felt I could invest the few additional minutes.
This is perhaps the most interesting and useful way to get skeleton entires up that I've heard. It fits quite well.
I'll ponder how to do it right.
The thing about stable filenames is just a django thing, it wants uploaded files to be 'sacrid' so you don't accidentally stamp over someone elses file. but it has their weird bug where you upload the same file again to exactly the same object and it just makes a new file. Inconvient.
Martin,