cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <>
Subject Re: usenpm and old versions
Date Fri, 27 Jun 2014 20:30:08 GMT
Download logic is part of the CLI for convenience, but there have been
several proposals to change this in the future.

Either way, Mark already added the awesome feature: `cordova platform add
/path/to/platform`, so you can already chose to fetch any version any way,
and install it that way.

I don't see value in releasing old versions to npm, we need more
motivations to get people to upgrade, and if there are valid reasons to
refrain, devs should speak up.  The ability to install at specific versions
I think is most useful for temporary transitions of apps to new releases,
and so the problem of installing old versions using non-npm flow I hope
goes away as we release the next (2?) releases to npm.

But as Ian said, the releases are on dist and have been voted on, so I
wouldn't be opposed to someone else putting in the rather trivial amount of


On Fri, Jun 27, 2014 at 10:13 AM, Gorkem Ercan <>

> On Fri, Jun 27, 2014 at 09:53:20AM -0400, Mark Koudritsky wrote:
> > Is it really worth it?
> Cordova packages are consumed in different ways. This will create the
> inconvinience of changing retrieval logic with versions for things like
> CI tools, and IDEs. It is just a matter of being kind to those folks.
> > git clone --branch=<your favorite tag> <platform-repo>
> > cordova platform add /dir/where/it/cloned
> > is not much longer and gives you full control at what version exactly you
> > are getting. In addition it provides an indication that this is not the
> > most recommended way and one should know what he is doing when explicitly
> > asking for an older version.
> Which raises the question why do we have download logic as part of the
> CLI at all?
> --
> Gorkem

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message