Thanks to @V1TA5, we have a mirror of the freely redistributable mods
from KS. This change re-writes extant CKAN metadata files that have
free licenses to use the i.52k.de server.
Created by running 1f3e252e9ae3dbad6e123d72dd1a255e32484a6e of
kspstuff-migrate.pl in https://github.com/pjf/KS-KSPStuff-Migration
These mods are:
1. All under FOSS licenses.
1. All present in our indexer, and so easily available for me to upload.
1. Now in a great big S3 bucket.
S3 buckets have interfaces that make me cry, and there's nowhere near as
many of these as I would like, but it's a start.
The S3 buckets I'm using will run out in a couple of years, so
longer-term we should migrate these to the Internet Archive. Yes,
they're cool with this (provided all the content is under a freely
distributable license), but it requires some fussing to get up and
running. So I've gone with S3 for now.
I've tested some, but not all of these. You can test them by going to
CKAN -> Settings and using a metadata repo of
`https://github.com/KSP-CKAN/CKAN-meta/archive/ks_recovery_1.tar.gz`.
Obviously only the migrated mods (see filelist) will work with this
migration. But it's a start.
As discussed in KSP-CKAN/CKAN#1156, sometimes we see older versions of
mods that have "generic" KSP versions (eg: 1.0), even though newer
versions of those same mods have specific versions (eg 1.0.1). These has
been a side-effect of how KS returns KSP version numbers to us.
This patch adds ".0" to version numbers if and only if we see a later
version of the same mod that has a specific version number in the same
sequence (eg: 1.0 and 1.0.3 causes a rewrite, but 0.24 and 1.0.3 does
not).
Source code coming soon. I haven't checked it into CKAN-meta because
it's not really a place where lots of code should be hanging out.
Also attn @dbent, who identified this issue in the first place.
