Exported environment is inconsistent (sometimes)

[g-arjones]

Exported environment may be different when running autoproj update --config and autoproj envsh. That happens because packages that are not yet imported are excluded from the selection during resolution when running autoproj envsh but that doesn't happen when the environment is exported after an autoproj update --config. The immediate and obvious fix for this is to just skip Package#update_environment while loading packages if a package is not checked out but I'm wondering whether the whole loading of non-imported packages (i.e dependencies processing) should be skipped as well.

@doudou What do you think?

[doudou]

I think what you say makes sense. Maybe just ignoring the non-imported packages would be enough...