troposphere needs to be changed to enforce the following constraint:
"For any package version N@V with earliestCompatibleVersion E, if
N@E is a published version, then its earliestCompatibleVersion is
also E."
In this way, earliestCompatibleVersion partitions the set of versions of
a package into compatibility classes. There's no need to do comparisons
on ECVs; instead, you just can check to see if two versions have the
same ECV.
This makes some of the ECV logic simpler.
It should not longer be allowed to depend on a version that does not
exist (although this should really be an immediate error instead of an
unsatisfiable constraint like it is with this commit).
bump dev bundle again
sigh. in trying to work around a silly bug (npm creates ~/tmp), it
turns out that you can't actually install npm like that --- because it
reverts the hack done by 'make install PORTABLE=1' to make npm find node
properly (because that hack literally rewrites a file in the npm module)
it is way too hard to get a non-portable package to work both from
uniload (which can't depend on non-core packages) and with meteor deploy
from checkout on mac (which basically requires a non-core package to
have the non-portability in it)
Changes:
- Drop keypress; it hasn't been used since we rewrote prompts to use
built-in readline
- Use a slightly newer version of npm, to avoid strange thing where it
creates ~/tmp
- Drop node-aes-gcm and bcrypt: we now can support cross-platform
package deploys directly! (A follow-up commit will add them
to the corresponding packages.)
- Drop heapdump: it was only there for convenience, and now can also be
added via a package
- upddate some comments
