usenpm and old versions

[Gorkem Ercan <go...@gmail.com>]

Hi All,
Is there a plan to provide the older Cordova versions of the platforms on
npm. At the moment only version 3.5.0 is available, I think one of the
value adds with usenpm is the ability to use older versions.
--
Gorkem

Re: usenpm and old versions

[Michal Mocny <mm...@chromium.org>]

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
effort.

-Michal


On Fri, Jun 27, 2014 at 10:13 AM, Gorkem Ercan <go...@gmail.com>
wrote:

> 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
>

Re: usenpm and old versions

[Gorkem Ercan <go...@gmail.com>]

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

Re: usenpm and old versions

[Mark Koudritsky <ka...@google.com>]

Is it really worth it?
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.

Re: usenpm and old versions

[Gorkem Ercan <go...@gmail.com>]

I imagine versions greater than 3.0.0 would be the target. I have doubts
that CLI can support earlier versions (may even choke on some of the >3.0.0
versions).

I am OK with uploading only the latest patched versions so that we would
have to do less.
--
Gorkem

On Fri, Jun 27, 2014 at 9:06 AM, Ian Clelland <ic...@chromium.org>
wrote:

> I don't think it's been discussed at all on this list, so no, I don't think
> there's a plan.
>
> If someone wanted to take the time to package them up, then I don't think
> they would be blocked at all. It was all "released" previously, so it's a
> matter of repackaging now.
>
> One topic of discussion for this list, though, would be which versions to
> make available? It might be considered poor form to add, say, any release
> which has unpatched reported security vulnerabilities. (But should be fine
> to add the version that includes the patch instead)
>
>
> On Fri, Jun 27, 2014 at 8:43 AM, Gorkem Ercan <go...@gmail.com>
> wrote:
>
> > Hi All,
> > Is there a plan to provide the older Cordova versions of the platforms on
> > npm. At the moment only version 3.5.0 is available, I think one of the
> > value adds with usenpm is the ability to use older versions.
> > --
> > Gorkem
> >
>

Re: usenpm and old versions

[Ian Clelland <ic...@chromium.org>]

I don't think it's been discussed at all on this list, so no, I don't think
there's a plan.

If someone wanted to take the time to package them up, then I don't think
they would be blocked at all. It was all "released" previously, so it's a
matter of repackaging now.

One topic of discussion for this list, though, would be which versions to
make available? It might be considered poor form to add, say, any release
which has unpatched reported security vulnerabilities. (But should be fine
to add the version that includes the patch instead)


On Fri, Jun 27, 2014 at 8:43 AM, Gorkem Ercan <go...@gmail.com>
wrote:

> Hi All,
> Is there a plan to provide the older Cordova versions of the platforms on
> npm. At the moment only version 3.5.0 is available, I think one of the
> value adds with usenpm is the ability to use older versions.
> --
> Gorkem
>