Open laktek opened 10 years ago
We removed parts init
for a reason https://github.com/nitrous-io/autoparts/commit/c27b21355fde53db4244ff4952de339f8648c45e
Can you make sure that we can auto-update with parts env
instead of reusing parts init
, maybe with parts env --update
or something ?
But there's a following commit https://github.com/nitrous-io/autoparts/commit/ca7839a8e386dfac63517b3dfeb51a40d1aabea9, which prevents parts init -
from auto-starting packages (reason stated in the commit that removed parts init -
).
So I guess it's safe to use parts init -
again.
I think this is fine except I'm not sure if we need to call parts init -
inside script/setup_buildenv
.
IMHO, the interface should be like this so that there are no surprises:
parts update
: updates Autopartsparts env
: prints env vars onlyparts init
: not sure what this will do nowBut we don't have to change this.
Before https://github.com/nitrous-io/autoparts/commit/c27b21355fde53db4244ff4952de339f8648c45e, script/setup_buildenv
also called parts init -
. So basically this reverts to the original behaviour (not really sure whether calling parts env
there is fine).
This reinstates the original behaviour of checking for updates (which is included in
parts init
) when starting a new shell.