Worked like a swiss... Car. On Mar 15, 2013 5:29 PM, "Filip Maj" <[email protected]> wrote:
> No problems on this end. Installed just fine! > > On 3/15/13 12:36 PM, "Brent Lintner" <[email protected]> wrote: > > >Looks like it is up! > > > >Although, the first time I installed it, I had a weird error where > >`bin/ripple` could not be found, and it was broken. > > > >Of course, it could of been an issue with npm and an old, local install of > >ripple (from the git repo). I made sure it was not installed, and also ran > >"npm cache clean ripple-emulator" to make sure. Everything seems to be > >working now. > > > >Anyone else see that? (hope not!). > > > >On Fri, Mar 15, 2013 at 3:31 PM, Dan Silivestru > ><[email protected]>wrote: > > > >> That's awesome. Thanks Mark :) > >> On Mar 15, 2013 3:30 PM, "Gord Tanner" <[email protected]> wrote: > >> > >> > NICE!!!!!! > >> > > >> > Reference link is here: https://npmjs.org/package/ripple-emulator > >> > > >> > > >> > > >> > On Fri, Mar 15, 2013 at 3:24 PM, Mark Dineen <[email protected]> wrote: > >> > > >> > > Hi everyone, > >> > > > >> > > The update has been released to NPM. Let me know if you encounter > >>any > >> > > issues. > >> > > > >> > > Cheers, > >> > > > >> > > Mark. > >> > > > >> > > > >> > > On Fri, Mar 15, 2013 at 2:09 PM, Brent Lintner < > >> [email protected] > >> > > >wrote: > >> > > > >> > > > Epic! Thanks Mark. :-) > >> > > > > >> > > > Once that is done, unless someone else wants to get it, I will > >>update > >> > our > >> > > > README, as well ( > >> > > > > >>https://github.com/brentlintner/incubator-ripple#cli--npm-package). > >> > :-) > >> > > > On Mar 15, 2013 11:05 AM, "Mark Dineen" <[email protected]> > >>wrote: > >> > > > > >> > > > > Hi everyone, > >> > > > > > >> > > > > I'd be happy to make the unofficial push to NPM. I'll make the > >> > release > >> > > > > this aft. > >> > > > > > >> > > > > Thanks, > >> > > > > > >> > > > > Mark. > >> > > > > Sent from my BlackBerry > >> > > > > +1 226 924 5232 > >> > > > > > >> > > > > -----Original Message----- > >> > > > > From: Dan Silivestru <[email protected]> > >> > > > > Date: Fri, 15 Mar 2013 11:00:46 > >> > > > > To: Ripple Dev List [ASF]<[email protected]> > >> > > > > Reply-To: [email protected] > >> > > > > Subject: Re: [DISCUSS] Publish Hosted Ripple on NPM > >> > > > > > >> > > > > Hi Jukka, > >> > > > > > >> > > > > Thanks for the feedback. I don't think we would want to do this > >>as > >> a > >> > > > > BlackBerry (RIM) release since we already have two tested > >> > distributions > >> > > > > [1][2]. We can do it as an individual release, however, being > >> > > BlackBerry > >> > > > > employees we would need to do some internal work to be able to > >>make > >> > it > >> > > > > happen and it would definitely take more then a few days. > >> > > > > > >> > > > > If members of our community (and Cordova's community) really > >>need > >> > this > >> > > > > published sooner rather then later, especially so that this can > >>be > >> > > easily > >> > > > > integrated with the Cordova CLI, I would like to ask on here if > >> there > >> > > are > >> > > > > any volunteers that could publish this to NPM as an individual > >> > release. > >> > > > You > >> > > > > would need to make sure, as Jukka said, that it is marked as a > >> > > non-apache > >> > > > > endorsed release. I would also ask that you add myself, Gord > >> Tanner, > >> > > > Brent > >> > > > > Lintner, and Fillip Maj as contributors. > >> > > > > > >> > > > > In the mean time, I think this should go through the proper > >>Apache > >> > > > channels > >> > > > > and I will start work on getting everything lined up for an > >>Apache > >> > > > release. > >> > > > > > >> > > > > Thoughts? Comments? > >> > > > > > >> > > > > Thanks, > >> > > > > > >> > > > > Dan. > >> > > > > > >> > > > > [1] https://developer.blackberry.com/html5/download/ > >> > > > > [2] > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> > https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphab > >>nejjhdalkjhgipohgpdnoc > >> > > > > > >> > > > > > >> > > > > On Tue, Mar 12, 2013 at 4:31 PM, Jukka Zitting < > >> > > [email protected] > >> > > > > >wrote: > >> > > > > > >> > > > > > Hi, > >> > > > > > > >> > > > > > On Tue, Mar 12, 2013 at 2:45 PM, Gord Tanner > >><[email protected]> > >> > > > wrote: > >> > > > > > > I decided to name the package ripple-emulator and have the > >> > command > >> > > > > still > >> > > > > > be > >> > > > > > > ripple > >> > > > > > > >> > > > > > An alternative to consider would be to name the package > >> > > apache-ripple. > >> > > > > > > >> > > > > > > If no one has any problems with this being published I will > >>get > >> > it > >> > > > into > >> > > > > > NPM > >> > > > > > > by the end of the week. > >> > > > > > > >> > > > > > There's a somewhat heavy process at Apache about when and how > >> code > >> > > > > > should get released to outside the development team, and > >>ideally > >> > we'd > >> > > > > > make sure that anything we push to NPM has gone through that > >> > process > >> > > > > > as it helps guarantee code and IP quality and provides legal > >> > shelter > >> > > > > > to the release manager and others involved in making the > >>release. > >> > > > > > > >> > > > > > That said, as seen by Cordova, getting through that process > >>the > >> > first > >> > > > > > time can be quite time-consuming (though I'd expect Ripple > >>with > >> > fewer > >> > > > > > complex dependencies to have an easier time with an Apache > >> > release), > >> > > > > > so if you want to do this within a few days, it's best if the > >> > release > >> > > > > > is clearly marked as a non-Apache one, made by you as an > >> individual > >> > > or > >> > > > > > perhaps RIM as a company. > >> > > > > > > >> > > > > > In either case it would be good if we started looking at > >>getting > >> > our > >> > > > > > first Apache release ready and shipping in near future. See > >>[1] > >> for > >> > > > > > information on what an Apache release is and what doing one > >> > requires, > >> > > > > > and [2] for some extra Incubator requirements. There's also an > >> > > > > > Incubator release guide at [3], but that document is > >> unfortunately > >> > > > > > rather unwieldy. > >> > > > > > > >> > > > > > [1] http://www.apache.org/dev/index.html#releases > >> > > > > > [2] > >> > > > > > >> > > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > >> > > > > > [3] http://incubator.apache.org/guides/releasemanagement.html > >> > > > > > > >> > > > > > BR, > >> > > > > > > >> > > > > > Jukka Zitting > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > -- > >> > > > > Dan Silivestru > >> > > > > +1 (519) 589-3624 > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > > > > > > >-- > >Brent > >
