Remove pinnings by build for all packages
I would like to propose pinning (internal) packages by build_string
.
The current solution allows to very precisely control which builds make it into the distribution, but the cost is very high when dealing with things like migrations to new upstream libraries. A concrete example is root
, which is fairly fast moving (new bug-fix releases every ~2 months) but also pinned exactly at build time. This means that whenever there's a root
migration from one version to the next, we need to move to new builds of all of those packages that build against root
, finding and updating these builds is (extremely) time consuming.
The alternative is to specify, for each package, the version
only, and let the build be selected by mamba
when the environment is rendered. This should effectively automatically pick up migrations (of all pinned packages, not just root
); the cost being that new builds of internal packages will be introduced without any control.
@rhys.poulton, @adam-mercer, @jameson.rollins, @stuart.anderson, do you have any feebback on this idea?