Havoc Pennington

The PR for this also needs to modify the publication_info() blob to move variables into the individual env specs.

see also https://github.com/Anaconda-Platform/anaconda-project/issues/53

anaconda-project itself doesn't know about this directory (you always have to pass a project dir in to anaconda-project), so this is implemented only in Navigator.

Though see https://github.com/Anaconda-Platform/anaconda-project/issues/47

Maybe it's an option for `add-env-spec`, like `anaconda-project add-env-spec --from-file=environment.yml` maybe.

The available solutions depend on exactly what you want to accomplish perhaps: * If libgcc is a transitive dependency (pulled in by another dep) you don't directly care about, then...

#86 (bootstrap environments) was the solution we had in mind for this in the past.

This is mostly fixed if you're using a lockfile, but if not using a lockfile we only check `=version` and not `>version` or `

One way to implement this would be to record all env spec hashes, apply changes (use_changes_without_saving()), and then reprepare any environment that has a different hash.

It may be more consistent if going down this road to make plain `anaconda-project prepare` prepare all environments instead of the default one.