[ 
https://issues.apache.org/jira/browse/CB-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105962#comment-14105962
 ] 

Josh Soref commented on CB-7363:
--------------------------------

Dunno.

a hypothetical cordova-cli 3.7.9 which wants cordova-lib ~3.7.8 would be happy 
w/ ~3.7.1000 (whereas before this change, it would have rejected it and 
retrieved 3.7.8), it wouldn't be any happier with 3.8 than it was before this 
change.

Mostly it depends on how we make version numbers. Given our current tendencies, 
this change is the minimal change necessary to not cause me hell. If we wanted 
to be looser, we could use {{>=}} instead of {{~}}, in which case 3.8 or 4.0 
would also be allowed. Making  that change would require an actual discussion, 
whereas, what we had now was fundamentally broken and interfering with my 
ability to fix mobilespec.

> Do not insist on precise version of cordova-lib
> -----------------------------------------------
>
>                 Key: CB-7363
>                 URL: https://issues.apache.org/jira/browse/CB-7363
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, Plugman
>    Affects Versions: 3.5.0
>            Reporter: Josh Soref
>            Assignee: Josh Soref
>
> Currently plugman's {{package.json}} has:
> {quote}
>     "cordova-lib" : "0.21.6",
> {quote}
> Unfortunately, my git repo (from coho) of {{cordova-lib}} has {{0.21.8-dev}}, 
> which means that if I do {{npm install}} in {{cordova-plugman}}, and I have a 
> _symlink_ to {{cordova-lib}} in its {{node_modules}}, the _symlink_ is 
> *obliterated*. This isn't desirable and makes a totally mess out of git 
> repositories.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to