Commit Graph

30 Commits

Author SHA1 Message Date
Emily Stark
b0e0ccb5a4 Bump package versions for 0.9.0.1 2014-08-27 15:16:49 -07:00
Emily Stark
1b639e5853 Bump package versions for 0.9.0.1-rc1 2014-08-27 14:28:03 -07:00
David Glasser
43e01c09eb Improve treatment of prerelease (dashed) packages
Drop the "at-least" constraint type entirely. It was not user-accessible
and was only used in the form ">=0.0.0" to represent a constraint with
no version constraint at all. This type of constraint is now called
"any-reasonable".

The definition of "any-reasonable" is:

  - Any version that is not a pre-release (has no dash)
  - Or a pre-release version that is explicitly mentioned in a TOP-LEVEL
    constraint passed to the constraint solver

For example, constraints from .meteor/packages, constraints from the
release, and constraints from the command line of "meteor add" end up
being top-level.

Why only top-level-constrained pre-release versions, and not versions we
find explicitly desired by some other desired version while walking the
graph?

The constraint solver assumes that adding a constraint to the resolver
state can't make previously impossible choices now possible.  If
pre-releases mentioned anywhere worked, then applying the constraints
"any reasonable" followed by "1.2.3-rc1" would result in "1.2.3-rc1"
ruled first impossible and then possible again. That's no good, so we
have to fix the meaning based on something at the start.  (We could try
to apply our prerelease-avoidance tactics solely in the cost functions,
but then it becomes a much less strict rule.)

At the very least, this change should allow you to run meteor on a
preview branch like cordova-hcp without getting a conflict between the
prerelease package on the branch/release and the lack of an explicit
constraint in .meteor/packages on that package, because we are
reintepreting the .meteor/packages constraint as meaning "anything
reasonable" and the in-the-release version counts as reasonable.
2014-08-26 21:54:48 -07:00
David Glasser
0542a3a9ea 0.9.0-rc13, now on METEOR@ 2014-08-24 21:21:09 -07:00
David Glasser
53a844770f version bump for rc11 2014-08-21 18:45:08 -07:00
David Glasser
628be93f61 fix tests that tested lies! 2014-08-21 17:09:23 -07:00
David Glasser
5d5d1876da De-dup package name/constraint parsing code
Now we can all any of them from even before uniload is ready in the tool

I <3 symlinks
2014-08-21 17:00:21 -07:00
David Glasser
5bc415c51a Improve package name/version parsing errors
We now throw more specific errors, consistent between both tools and
package-version-parser (copy-and-pasted code, sadly, but we really do
have to make this check before uniload-from-checkout).
2014-08-21 16:21:12 -07:00
David Glasser
d8ff20103d version bumps (pre rc10)
We'll make rc10 tomorrow, but I want to build a release just to play
with built releases again.
2014-08-18 20:48:43 -07:00
David Glasser
f39a820d96 Don't parse '@>=' ranges by default
They are still used internally by the constraint solver (to implement
update --breaking) but cannot be externally specified.

Also, stop supporting "@none", whatever that was.
2014-08-15 22:12:04 -07:00
David Glasser
bc6239dfc1 vbump for rc9
Hopefully we won't have to do "bump for all the npm modules" again after
this
2014-08-15 12:34:47 -07:00
David Glasser
a9db15a9e6 vbump for 0.9.0-rc8 2014-08-14 12:02:08 -07:00
David Glasser
e59fb948b5 fix tests broken by 6850b679e9 2014-07-30 19:24:55 -07:00
David Glasser
4428f2b06d sync tests passes 2014-07-24 17:12:14 -07:00
David Glasser
6850b679e9 fix bug in 'meteor add x@=1.0.0'
Used to print a "avoid conflicting dependencies" message. Now doesn't.

Start moving some uses of splitConstraint to parseConstraint
2014-07-24 16:21:25 -07:00
ekatek
b9a714f028 ripping out internal, name and test from package.js files 2014-07-07 20:50:50 -07:00
ekatek
fb709c9563 remove versions files from core packages 2014-06-16 22:11:31 -07:00
David Glasser
d80452e50b don't try to run package-version-parser on client, it uses npm 2014-06-11 12:13:20 -07:00
David Glasser
8e2c97cd58 meteor update sorta works sometimes 2014-05-20 11:09:53 -07:00
Slava Kim
98d9a56a62 Extend the number of types of constraints from 2 to 3
Instead of having a "exact" flag, have a "type" field with 3 different values
2014-05-15 18:16:30 -07:00
ekatek
47834a4f6e add underscore to constraint solver test dependency and also versions files 2014-05-09 17:44:36 -07:00
ekatek
beb0e59b9d new version files from teh new solver? Also, package.js correct with tests 2014-05-09 17:36:25 -07:00
ekatek
f2d3972857 integration mostly works except for bizarre constraint solver output bug 2014-05-09 15:15:45 -07:00
Geoff Schmidt
985ffea9fa WIP - make package build run the constraint solver.
move constraint solver from a package into the tool.
unipackage loading is broken; next step is to fix that
2014-03-12 19:02:47 -07:00
Geoff Schmidt
66b7253695 Take all packages to 1.0.0 (that aren't already there) 2014-03-07 12:00:20 -08:00
Slava Kim
926305bae0 Support "none" dependencies (no constraint) 2014-03-07 00:17:19 -08:00
Geoff Schmidt
63f13fbb87 Create the Catalog object 2014-03-06 21:56:47 -08:00
ekatek
876276418a add-pakage refined 2014-03-06 18:02:14 -08:00
Slava Kim
9dd40fa1db extract parseVersionConstraint from parseConstraint 2014-03-05 01:25:51 -08:00
Slava Kim
468f32bd80 package-version-parser package
first version of a package that parses smart package version string
2014-03-04 23:08:38 -08:00