hisaishi-kanade
/
CKAN-meta
mirror of https://github.com/KSP-CKAN/CKAN-meta.git
1
0
Fork 0
Code Releases Activity
CKAN-meta/TechManager/TechManager-1.5-compat.ckan

18 lines
803 B
Plaintext
Raw Normal View History

TechManager compatibility file for 0.90 Nobody ever¹ has had any problems with TechManager 1.5 for 0.90, and the author hasn't been seen in WEEKS. Since evrything good in the world² uses TechManager and the Community Tech Tree, here's a compatibility shim that will install v1.5 for 0.90. "Why not change the existing metadata?", I hear you ask. Mainly it's because it's generated by netkan, and if KerbalStuff ever gets updated, or if the metadata ever gets regenerated, we don't want anything to break. Many thanks to Daz for the prompting. Attentioning @NathanKell, because relevance. Also, this means I might finally upgrade to KSP 0.90. ¹ Allegedly. ² RP-0
2015-01-28 11:41:10 +00:00
{
"spec_version": 1,
"identifier": "TechManager",
"resources": {
"homepage": "http://forum.kerbalspaceprogram.com/threads/98293-0-25-TechManager-Version-1-0",
"kerbalstuff": "https://kerbalstuff.com/mod/297/TechManager"
},
"ksp_version": "0.90",
"comment": "Nobody's had problems running TM 1.5 under 0.90, so this is a compatibility shim to allow it to be installed. Once TM 1.6 comes out, CKAN users should be able to install without pain.",
"name": "TechManager",
"license": "MIT",
"abstract": "This mod will allow you to change the tech tree, including the creation of new tech nodes. ",
"author": "anonish",
"version": "1.5-compat",
Patial recovery of KS mods. 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.
2016-02-16 08:11:05 +00:00
"download": "https://s3-us-west-2.amazonaws.com/ksp-ckan/DD419605.zip",
TechManager compatibility file for 0.90 Nobody ever¹ has had any problems with TechManager 1.5 for 0.90, and the author hasn't been seen in WEEKS. Since evrything good in the world² uses TechManager and the Community Tech Tree, here's a compatibility shim that will install v1.5 for 0.90. "Why not change the existing metadata?", I hear you ask. Mainly it's because it's generated by netkan, and if KerbalStuff ever gets updated, or if the metadata ever gets regenerated, we don't want anything to break. Many thanks to Daz for the prompting. Attentioning @NathanKell, because relevance. Also, this means I might finally upgrade to KSP 0.90. ¹ Allegedly. ² RP-0
2015-01-28 11:41:10 +00:00
"download_size": 39956
}