Check for updates when starting a new shell.

[laktek]

This reinstates the original behaviour of checking for updates (which is included in parts init) when starting a new shell.

[dqminh]

We removed parts init for a reason c27b213

Can you make sure that we can auto-update with parts env instead of reusing parts init, maybe with parts env --update or something ?

[laktek]

But there's a following commit ca7839a, 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.

[chuyeow]

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 Autoparts
• parts env: prints env vars only
• parts init: not sure what this will do now

But we don't have to change this.

[laktek]

Before c27b213, 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).

[keyist]

Because parts_init var is changed here, line 32 file.include? parts_init condition will mean that the file can potentially have two lines, one for evalling parts env the other for evalling parts init.

Which I guess is fine, but something to watch out for in the future if we change it back.

[laktek]

hmmm..but I guess it would be rare for someone to run the setup script, if they have Autoparts already installed?