Recent changes make ws.manifest.main_package_set invalid in package sets init.rb

[pierrewillenbrockdfki]

The changes to configuration.rb in commit c7b291c, merged with #335 make ws.manifest.main_package_set nil during execution of package sets init.rb, because the main package set is added last.

Is this change acceptable from autoproj point of view?

This could be fixed by splitting the for loop in two, so the init.rbs get called after all package sets have been re-added.
@2maz

[pierrewillenbrockdfki]

Turns out, this is expected behaviour/change.

[doudou]

@2maz since we already know what's the main package set, and because the main package set is the one that is being imported first (always), can't we set it anyways ?

[g-arjones]

Just out of curiosity why would you want a reference to the main package set in another package set?

I mean, referencing any package set that is not the current one feels like a bad idea to me

[pierrewillenbrockdfki]

DFKI has some custom machinery implemented in a package set that would create new files in autoproj/override.d. It uses the main_package_set to trigger a reload of these files. As far as i understand, this machinery will be made obsolete by #336 .