Skip to content
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

FR: Allow more exact version requirements. #194

Open
EatThePath opened this issue May 22, 2020 · 1 comment
Open

FR: Allow more exact version requirements. #194

EatThePath opened this issue May 22, 2020 · 1 comment

Comments

@EatThePath
Copy link
Contributor

It appears that if you specify version X.Y.Z for a mod dependency, even if you don't pick newest, Knossos treats the Z requirement as an >= test rather than an == test. This has caused a lot of problems with mods making changes they viewed as minor fixes that caused major headaches down the chain, most often with BP-dependant mods after BP adapts to new MVPs versions.

It's possible to force knossos to be pickier, but only with direct edits to the mod.json file, and these edits seem to cause issues at the downloading stage. It'd be much preferable to have a built in, supported strict versioning option.

@ngld
Copy link
Owner

ngld commented Jun 7, 2020

I'd actually like to enforce a == check for all dependencies except FSO. That would simplify the dependency logic in Knossos and probably fix a lot of installation issues. However, that means that after a new MVPs release, all mods that use them (AKA most) will have to update their mod dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants