(still outstanding: changes to package publication workflow)
A package marked debugOnly in the package source is not to be bundled in production.
Moreover, if a package/app depends on a debugOnly package, that entire tree should
not be bundled. (But we should take it into account when figuring out versions!)
Does the following:
- In the catalog, we have a function that takes in a set of versions and a set of original
constraints and traverses it, recursively, to build a subset of versions that we *should*
bundle, and the corresponding subset of versions that we shouldn't (because they are either
debugOnly themselves or pulled in by debugOnly packages). (We do this in the catalog because
it is an addon onto the results of the constraint solver, tied deeply into our representation
of data)
- In the packageLoader, we keep track packages & versions that we should bundle, and also,
packages that we should exclude. We do this in the package-loader because, essentially, that's the
object that we use to keep the results of the constraint-solver, and we already propagate it to all
functions that care about it. (Possibly we should subsequently rename it later).
- In the compiler, when we figure out buildTimeDependencies, we ask if we need to bundle debug
builds. If not, we filter them out (see above). Also, when we actually build together unibuilds,
we don't touch the ones that the packageloader tells us to exclude (which ensures that they don't make
it into the final product).
- In the project, we keep track of whether this project is building in debug mode. That's because the project
is where we keep the state of our curent project that we are building, and if we are ever in the state of
building multiple things, then that's the code that we would need to touch (see also that we make a similar
assumption when solving constraints).
- Adds the option to keepthe project debug-build-free and calls it in commands when approporiate.
1. Add README files for both the ios/ and android/
subdirectories of a build directory linking to a
Wiki page with instructions on how to go through
the publish process for both app stores.
2. To make the README file more visible in iOS projects,
and to make the ios directory tree mirror the android
one, place what used to go in <BUILD DIR>/ios/ into
<BUILD DIR>/ios/project/. <BUILD DIR>/ios/ now only
contains the README file.
This sentence is about ECV but nothing else in the docs discusses ECV
and it doesn't use that term. So it's actually kind of confusing; to me,
it suggested that asking for `1.2.3_1` might give you `1.2.3`, which is
not true.
Old:
$ curmeteor add iron:router@9.9.9
Got error during resolve; trying refresh { [Error: conflict: constraints on iron:router cannot be satisfied.
Constraints come from:
<top level>] constraintSolverError: true }
Could not satisfy all the specified constraints:
Error: conflict: constraints on iron:router cannot be satisfied.
Constraints come from:
<top level>
New:
$ curmeteor add iron:router@9.9.9
iron:router@9.9.9: no such version
We started calling our releases 0.9.3.1-rc.0 to match what you need to
do in semver to get proper numeric comparisons; let's make sure to
create orderKeys that work with them.
