Coverage Question Part 2

Nobody has claimed this yet.

Thanks for the quick reply!
Long term, I hope Meteor will be 100% npm so this issue goes away. For now, I need something that is easy, robust and allows for developers to build locally on their dev. boxes (which can be mac, linux or windows). With that in mind, maybe stratosphere is the right way to go?

If you think stratosphere could be augmented without a ton of work to cache the upstream stuff, would you please be able to provide some code snippets or an idea of all the touch points before I go off and review the code? Alternatively, I assume one could fetch the public package and locally publish to stratosphere. However, the downside is that version updates would be manual.

Finally, note that I am looking into caching the meteor installers as well since these should be backed up as well. This too will require writing a server if I want automatic upstream fetching :-) Possibly could add this to stratosphere.

Thanks in advance.

The issue names no files, tests, or entry points. First inspect the stratosphere package-server implementation and its handling of upstream packages; done would require a decided, cross-platform approach for caching package and installer downloads with clear update behavior.

Written by the indexing model from the issue text.