[Feature] Ability to install from .ckan file for ConsoleUI about ckan HOT 14 OPEN

Try ckan install -c modpack.ckan from the command line.

Edit: -c, not -f.

from ckan.

I tried both -c and -f, and both just showed the usage options as if they were not recognized. This is how I am running it:

./CKAN.app/Contents/MacOS/CKAN instance default lifeboat
Successfully set "lifeboat" as the default game instance

./CKAN.app/Contents/MacOS/CKAN -c lifeboat-modpack.ckan
CKAN-CmdLine 1.31.2
Copyright © 2014–2022
Usage: ckan <command> [options] 
... [text deleted]

Setting the instance from the command like this way looks like it worked.

from ckan.

@wright You missed the install part of the command

from ckan.

Thanks! There is some progress. It runs if I give it an absolute path to the .ckan file. But, it complains about unsatisfied dependencies and the two suggested workarounds don't seem to do anything:

./CKAN.app/Contents/MacOS/CKAN install --allow-incompatible -c /Applications/addons/games/KSP_osx_1.12.5_lifeboat/lifeboat-modpack.ckan
lifeboat-modpack dependency on AT-Utils version (any) not satisfied
If you're lucky, you can do a `ckan update` and try again.
Try `ckan install --no-recommends` to skip installation of recommended modules.
Or `ckan install --allow-incompatible` to ignore module compatibility.

CKAN update` says that everything is up to date.

from ckan.

Try updating your compatibility to match what the modpack file says in the ksp_version_min and ksp_version_max properties.

from ckan.

The mod pack says:

"ksp_version_min": "1.12.5",
"ksp_version_max": "1.12.5",

I updated the compatibility in CKAN to list 1.12.5.3190 (as suggested in the drop down box, although it displays after adding it as 1.12.5.319) and 1.12.5 (manually), and got the same result.

from ckan.

That's very odd, since AT-Utils apparently only goes up to 1.10, so it wouldn't normally be installable in the original copy of hte game with those settings. Maybe the mod was installed via the checkbox in the Versions tab to override the compatibility?

from ckan.

I'm not sure, I did not generate the mod list. I would expect --allow-incompatible to work around that in any case.

from ckan.

--allow-incompatible only affects the mods immediately listed on the command line, not dependencies.

from ckan.

Is there a way to skip dependencies?

from ckan.

No. Going by AT-Utils' compatibility, you could try this instead:

ckan compat add 1.10
ckan compat add 1.11
ckan compat add 1.12

from ckan.

That worked to get passed the AT-Utils problem, but it failed on another dependency.

Thanks for the many suggestions, but I think that my bad example .ckan file is obscuring the actual issue: the ConsoleUI does not support importing a mod list from an exported .ckan file.

The command line process (even if it worked with a good .ckan file) is not the ideal user experience, and it is currently the only option available for MacOS KSP CKAN users. It might save a lot of exasperation if the ConsoleUI could be expanded to:

• add an "Import mod list" menu item,
• that prompts for a .ckan file to read,
• then the file name is passed to the existing code that processes the list

Check Boxes could be added near the file name prompt for options such as --allow-incompatible. Error messages could be displayed in the same manner as other ConsoleUI errors.

from ckan.

Don't worry, nothing's being obscured; this issue is still a marker for adding that feature to ConsoleUI. I'm just trying to provide workarounds to get you going while the functionality does not exist.

from ckan.

I appreciate your help. I am going to give up on this particular .ckan file.

from ckan.