Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of shazron@gmail.com designates
 209.85.216.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEeF2Tco0cym9i6D4_jLXwcaRE=KmBG06Gw2DNPz0z0CH_rArg@mail.gmail.com>
References: 
 <CAMSbhBjsZ-Cn-GziKZRGDbm209ThYQ0A1XSuGBgG-6pJCD_T9w@mail.gmail.com>
 <CAE6O_-aMvMf9VSne4MnZHeOMzghmf+xjnvhxXmMJN2kk9RKg6w@mail.gmail.com>
 <CAKP6k2vd0WZdkB4GmOUV0E03BRbdkh3UhTV3iED6tTZ3tYZyRQ@mail.gmail.com>
 <CAMA9xmhErgPOiWYnkuhQY1E52ZtYcq24MJccuZO6XhsxjDLb+g@mail.gmail.com>
 <CAE6O_-bors+FkyJnwv0ki4r9N7XJn+UQKDSx0-QRgkax8Wu-Zw@mail.gmail.com>
 <CAKij_Rp_UwCjVzo9BHHtGeMOC3FCbg8Jy4u9D2syzJ4rhauKiw@mail.gmail.com>
 <CAKP6k2tqRX7UTvUhUpuhK_43ERyNqdHKmsVzi_TAqd5zLTuiSA@mail.gmail.com>
 <CAE6O_-YasbVGZGw-PFj++i6cSnccZJbz9ZNBLc0bRxknniu-rg@mail.gmail.com>
 <CAKP6k2s_5xJJTzgqEGXTsEb-Bo8SBA4VgnAOJQLBP=YxBuP04Q@mail.gmail.com>
 <CAE6O_-asSuuTA0dC4jBxQOSSd19kbpspW-Bcdi0t_V_obE4=Dg@mail.gmail.com>
 <CAEeF2Tco0cym9i6D4_jLXwcaRE=KmBG06Gw2DNPz0z0CH_rArg@mail.gmail.com>
From: Shazron <shazron@gmail.com>
Date: Tue, 12 Aug 2014 13:46:32 -0700
Message-ID: 
 <CAE6O_-aqz7mqW2mytRMMKabxT1NfYNYSoZyFSYHDpzW_LG9u9A@mail.gmail.com>
Subject: Re: Remove VERSION file from repos
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: text/plain; charset=UTF-8

Believe me, I want to go all node -- but all in for all scripts --
which we don't have time to do yet (maybe 4.0?).
But seeing that it's just replacing the contents of the current bash
script with python code, it's the path of least resistance, and path
of least potential conflict imo. No one will notice.


On Tue, Aug 12, 2014 at 1:36 PM, Michal Mocny <mmocny@chromium.org> wrote:
> Shaz, that's technically true, but how many users actually use that path
> these days?
>
> I thought the last stats overwhelmingly suggest our users are drinking the
> kool-aid and using cli, node, etc.
>
>
> On Tue, Aug 12, 2014 at 4:19 PM, Shazron <shazron@gmail.com> wrote:
>
>> Not if they are installed manually. It's not worth having some
>> dependency just to read a version, that's nuts.
>>
>> On Tue, Aug 12, 2014 at 1:15 PM, Jesse <purplecabbage@gmail.com> wrote:
>> > the non-cordova cli path depends on node to install/uninstall plugins
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Aug 12, 2014 at 1:08 PM, Shazron <shazron@gmail.com> wrote:
>> >
>> >> Of course I considered nodejs, but no, this is for the non-cordova CLI
>> >> path, which does not need another dependency.
>> >>
>> >> On Tue, Aug 12, 2014 at 11:52 AM, Jesse <purplecabbage@gmail.com>
>> wrote:
>> >> > Yeah, if you are going to replace bash, replace it with nodejs!
>> >> >
>> >> >
>> >> > @purplecabbage
>> >> > risingj.com
>> >> >
>> >> >
>> >> > On Tue, Aug 12, 2014 at 11:48 AM, Myles Borins <myles@famo.us> wrote:
>> >> >
>> >> >> Have you considered writing a small node script to pass the json?
>> This
>> >> >> would make it as simple as requiring in the package json an piping
>> the
>> >> >> relevant info to stdout
>> >> >> On Aug 12, 2014 11:47 AM, "Shazron" <shazron@gmail.com> wrote:
>> >> >>
>> >> >> > Yeah I value life and my sanity - I'll probably replace the bash
>> >> >> > script with python
>> >> >> >
>> >> >> > On Tue, Aug 12, 2014 at 11:40 AM, Lorin Beer <lorin.beer@gmail.com
>> >
>> >> >> wrote:
>> >> >> > > one source for version information is better
>> >> >> > >
>> >> >> > > although parsing json with bash scripts seems janky
>> >> >> > >
>> >> >> > >
>> >> >> > > On Tue, Aug 12, 2014 at 11:31 AM, Jesse <purplecabbage@gmail.com
>> >
>> >> >> wrote:
>> >> >> > >
>> >> >> > >> I think it still needs to exist in an output project ... which
>> is
>> >> not
>> >> >> > >> (yet?) an npm project, and so does not have a package.json.
>> >> >> > >>
>> >> >> > >> The individual platform repos can get rid of it, they will just
>> >> need
>> >> >> to
>> >> >> > >> modify the way they `create` new projects to read the value from
>> >> >> > >> package.json and output it to NewProject/VERSION
>> >> >> > >>
>> >> >> > >>
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> @purplecabbage
>> >> >> > >> risingj.com
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> On Tue, Aug 12, 2014 at 11:25 AM, Shazron <shazron@gmail.com>
>> >> wrote:
>> >> >> > >>
>> >> >> > >> > For iOS, the only file I can see that depends on this is:
>> >> >> > >> >
>> >> >> > >> > 1.
>> >> >> > >> >
>> >> >> > >>
>> >> >> >
>> >> >>
>> >>
>> https://github.com/apache/cordova-ios/blob/master/bin/templates/scripts/cordova/version
>> >> >> > >> >
>> >> >> > >> > Not sure of the alternative.
>> >> >> > >> >
>> >> >> > >> > This references it but can be removed:
>> >> >> > >> > https://github.com/apache/cordova-ios/blob/master/bin/create
>> >> >> > >> >
>> >> >> > >> >
>> >> >> > >> > On Tue, Aug 12, 2014 at 11:19 AM, Steven Gill <
>> >> >> stevengill97@gmail.com
>> >> >> > >
>> >> >> > >> > wrote:
>> >> >> > >> > > Most of our repos have a package.json. It keeps track of
>> >> >> versions. I
>> >> >> > >> > think
>> >> >> > >> > > we should work towards removing the VERSION files from the
>> >> repos
>> >> >> we
>> >> >> > >> can.
>> >> >> > >> > >
>> >> >> > >> > > Thoughts?
>> >> >> > >> > >
>> >> >> > >> > > This would require some changes to coho so it doesn't try to
>> >> >> update
>> >> >> > the
>> >> >> > >> > > version file when doing releases.
>> >> >> > >> >
>> >> >> > >>
>> >> >> >
>> >> >>
>> >>
>>