Meteorite not installing on node 0.8.8 about meteorite

[possibilities]

Ah, Ok, it's coming in through ddp... will push out a new release that should fix this in a few...

[possibilities]

Can you try .14?

[possibilities]

Mate that .15

[badslug]

Yup, that fixed it - everything working fine now. BTW, the meteorite repo on github has suddenly vanished. Did you make it private or something?

-iain

On Aug 24, 2012, at 2:08 AM, Mike Bannister [email protected] wrote:

Mate that .15

—
Reply to this email directly or view it on GitHub.

[possibilities]

Yay! So the other issue you reported with underscore.string is all set too?

P.s. Moved to org account https://github.com/oortcloud/meteorite https://github.com/oortcloud/atmosphere

[badslug]

Yes, it does solve the problem I had with underscore.string as well (looks like the older version of meteorite running on the incompatible newer version of node was at fault - not sure if there is any way to detect running on an incompatible version of node and asking to upgrade automatically).

Cool, makes sense to move it to an org account where everything is grouped together. One suggestion would be for you to create a meteorite and atmosphere project under your personal account and just put a README in each pointing to the new org repos. Otherwise all our old links in the google groups and websites etc that refer to the old URLs will get 404s.

[possibilities]

yes, will do that thanks!

also, yes, when i fix the --version thing you talked about i'm gonna make atmosphere yell at you if you're using an old version of mrt

[badslug]

Cool, I saw the ticket for old version detection - that will be very handy. It was a bit funny because Tom was helping troubleshoot the issues I was having with underscore-string and asked what version of meteorite I had installed - and I asked him how to tell, and he thought about it a bit and then realized he didn't know how to get the version number from an installed meteorite. :)

I suppose even longer term - it may help to think about how to version smart packages to atmosphere versions to handle the case where a smart package is made for a version of atmosphere/meteriorite and is not updated if/when atmosphere/meteorite is updated and the tools are incompatible with older smart packages. I know meteorite is a temporary tool until meteor gets the same functionality but it's feeling like we'll be so far along with meteorite that meteor will just adopt and incorporate meteorite (like how Node folded in npm).