mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
65c8b481e2
Small follow-up to #9018. Note (especially @GeoffreyBooth): these version constraints do two things: (1) specify a minimum version, and (2) fix the major version. In other words, the coffeescript package should not need to be republished when we publish new minor versions of these core packages in Meteor 1.5.2 or 1.6. When/if we publish a new major version of these packages, the coffeescript package can simply bump its version constraints, but that probably won't happen any time soon. I think that's reasonable because a major version bump suggests there are some significant changes that need to be acknowledged by dependent packages.
As of Meteor 0.9.0, Meteor supports packages with OS-specific builds (such as packages that use binary npm modules). This allows you to deploy apps from one platform to another, as long as the package has already published to the package server in the appropriate target architecture. However, this only works if the package can be loaded from the server at all; it does not work if the package is only available as local source code in your app, or in the main meteor tree if you're running meteor from a git checkout. Specifically, this means that packages *in the Meteor core* which have OS-specific dependencies will prevent apps from being deployed, if meteor is being run from the git checkout. To simplify this, we're taking the OS-specific dependencies of core packages and moving them to these packages, which are *NOT* in "the core". In order to run meteor from a checkout, these packages must be already published to the server. Fortunately, they won't change very frequently.