-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing parts to sub-folders #315
Comments
Oh my. This is why I wish we had a mod-packaging standard. (I'm hoping that greater adoption of the CKAN would help drive such a standard, which would be great even for non-CKAN users.) Right now, we don't have a good way of doing this, and while I know this has come up a few times before, I don't think we have a ticket for it yet. My suggestion is that we extend the
I'd suggest the following behaviours:
Does that sound reasonable? |
That sounds reasonable to me, and indeed was one of the approaches I was thinking of. It does seem very highly intuitive, since the install_to already looks like a path. Frankly I feel that the directory structure of the ASET_Parts is a bad idea. In practice I bet many people drop the ASET_Parts folder directly into GameData, and wonder why it does not work. |
This time testing where things should go, and more testing of bad paths.
* origin/master: Updated Spec to include v1.2 GameData paths. Removed warnings from the compiler abour our test cases. Spec copyediting for v1.2 and Gamedata/Paths Fix GameData/.. bug Test: GameData/.. should not be allowed. Tests that we handle KSP v1.0.0 correctly. Allow KSP versions to miss their leading zeros. Makes the checks more rational Adds subfolders to human-readable spec Passes all tests related to installation Additional tests for GH #315. Tests for extended GameData installs. Tests: Slight refactor ModuleInstaller tests. Added Bad target test. Allows GameData subdirs
This is now fixed in dev, and will be in 1.2.0. Thanks, @Ippo343! |
Thank you! :) Da: Paul Fenwickmailto:notifications@github.com This is now fixed in dev, and will be in 1.2.0. Thanks, @Ippo343! Reply to this email directly or view it on GitHub: |
* origin/master: Updated Spec to include v1.2 GameData paths. Removed warnings from the compiler abour our test cases. Spec copyediting for v1.2 and Gamedata/Paths Fix GameData/.. bug Test: GameData/.. should not be allowed. Tests that we handle KSP v1.0.0 correctly. Allow KSP versions to miss their leading zeros. Makes the checks more rational Adds subfolders to human-readable spec Passes all tests related to installation Additional tests for GH KSP-CKAN#315. Tests for extended GameData installs. Tests: Slight refactor ModuleInstaller tests. Added Bad target test. Allows GameData subdirs
A small number of mods require that they be installed in some specific sub-directory of GameData, but do not have that sub-directory included in the zip file. A good example of this is ASET_Parts, which is a mod used by several EVA enhancing mods and ALCOR's IVA view in particular. The files in that plugin must be installed to
GameData/ASET/ASET_Parts
but the top level folder in the plugin zip is theASET_Parts
folder itself.This is blocking my attempt to package the ALCOR mod, since ASET_Parts is a dependency (see KevinCathcart/CKAN-meta@ef80f4c )
The text was updated successfully, but these errors were encountered: