Martin v. Löwis wrote: > Erik Heneryd wrote: > >> Yes, those with older, bzip2less systems can probably figure out how >> to get it and build it, but why force them when it's practically no >> work keeping it? It's one (sic) extra command for the release manager >> and ~9M extra disk space per release on www.python.org. > > > Fred wouldn't have asked if it was no effort in keeping it. There is > certainly more than one command to it - you have to md5sum the file, > and copy the md5sum into the release notes. You have to upload the file > from your workstation to python.org. I don't know how you do that, but > I need to use my DSL link for uploading the MSI files; it takes roughly > 30min to upload. Fortunately, I have a DSL flatrate. > > Regards, > Martin Yeah, I was a bit hasty. Sure, it's more than one command: * pack it * unpack it * diff it against the known-to-be-good bzip2 tree * md5sum it and add that to the release notes * add another link on the download page * ...something else? but I still think my point stands - it's not that much work, really, and it'd be a nice service to those with bzip2less systems. Regarding upload times I guess I'm just another spoiled swede; I've been on ethernet for so long I can barely remember what 5k/s was like... That said, I do realise that it all adds up and that doing a release take some work, so whether you decide to keep it or not: thanks. Erik
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4