Using "Update" on a manually-installed NearFutureSolar will fail to install NearFutureSolarCore
JonnyOThan opened this issue · comments
- Manually install Near Future Solar
- Have CKAN auto-detect it:
- Click "update all" and apply:
- Let CKAN overwrite everything it wants:
- All 4 mods are now in CKAN's registry:
- NearFutureSolar.dll (i.e. NearFutureSolarCore) is missing:
I suspect that this might be because NearFutureSolar.dll has the same name as the NearFutureSolar
module identifier, but it's actually a different mod. Note that B9PS and ModuleManager were correctly installed, and I'm not aware of any functional difference in how those would have worked.
Related: KSP-CKAN/NetKAN#9922
In an attempt to prove or disprove the hypothesis that the name is the trigger, I tried the same experiment with CryoTanks (which also has a "core" dll, but it's named SimpleBoiloff.dll so it doesn't match any module identifiers).
- Manually install CryoTanks and all its dependencies (they're bundled, so this is easy)
- Create a text file in GameData and name it CryoTanks.dll
- Hit refresh in CKAN, it should auto-detect CryoTanks
- Hit "update all" and "apply"
- Let it overwrite everything
The SimpleBoiloff.dll (cryotanks-core) is installed correctly.
Hunch: is it installing NearFutureSolarCore first since that's a dependency, and then when it goes to remove and reinstall NearFutureSolar does it delete the auto-detected DLL (which is now actually the one owned by NearFutureSolarCore)?
Just confirmed the same thing happens with RasterPropMonitor and RasterPropMonitor-Core