-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
tried to install kanso_home to mess around with it and got an error when doing kanso fetch :
mandric in ~/dev/demos/kanso_home
$ kanso fetch
skipping modules (already exists)
skipping properties (already exists)
skipping attachments (already exists)
skipping settings (already exists)
Error: Conflicting version requirements for duality
kanso_home requires: 0.0.12
Currently installed version: 0.0.9
at /Users/mandric/local/node/lib/node/kanso/src/kanso/commands/fetch.js:100:41
at /Users/mandric/local/node/lib/node/kanso/src/kanso/settings.js:18:9
at /Users/mandric/local/node/lib/node/kanso/src/kanso/utils.js:176:9
at [object Object].<anonymous> (fs.js:107:5)
at [object Object].emit (events.js:61:17)
at afterRead (fs.js:878:12)
at wrapper (fs.js:245:17)
Failed
Ok, this may be a lesson in kanso packaging for me.
So kanso_home has duality:null in its kanso.json file which translates to latest version, so kanso complains? Secondly, I don't need to do kanso fetch for kanso_home because it already has the packages committed to the repo. But fetch should be happy, so I think the proper fix here is one of the following:
- update kanso_home/kanso.json with duality:"0.9.0" exact version number and the other packages as well
- make fetch ignore version numbers when duality:null or a null value is used for a dependency, so if a local package is present just accept it. null probably shouldn't translate to requiring the latest?
- make it a convention that if you define/package your own local packages you include exact version numbers in the local packages
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels