Now that I think I have a better understanding of the dependency chain,
lets try to create more. Ideally, we want to control what version(s) of
libMesh folks receive, based on what is available to moose-env/moose-dev
combinations.
Without that dependency chain, there is no dependency information between
moose-env --> moose-dev --> moose-libmesh (any update to libmesh, would
propagate to all users, regardless of what moose-env has configured, becuase
moose-env has no configuration).
Trigger a libMesh build, by downgrading the version. Once/if this passes, we
will trigger another build by adding a version to moose-dev's conda_build_config,
and bumping the moose-libmesh version. See what happens.
Also, while we know the compilers are slow, add them back in for now. Speed-up
is going to have to wait until we know conda-dependencies is going to work
for us.
Now that I think I have a better understanding of the dependency chain, lets try to create more. Ideally, we want to control what version(s) of libMesh folks receive, based on what is available to moose-env/moose-dev combinations.
Without that dependency chain, there is no dependency information between moose-env --> moose-dev --> moose-libmesh (any update to libmesh, would propagate to all users, regardless of what moose-env has configured, becuase moose-env has no configuration).
Trigger a libMesh build, by downgrading the version. Once/if this passes, we will trigger another build by adding a version to moose-dev's conda_build_config, and bumping the moose-libmesh version. See what happens.
Also, while we know the compilers are slow, add them back in for now. Speed-up is going to have to wait until we know conda-dependencies is going to work for us.
Refs #27