Opposite override order for osdeps vs autobuild packages?

[moooeeeep]

In order to check out the overriding/precendence behavior of autoproj, I designed a simple buildconf configuration with two package sets that each define a package and an osdep with the same name.

I noticed output during aup that indicates overriding behavior, which seems counterintuitive to me:

WARN: osdeps definition for setuptools, previously defined in /opt/workspace/autoproj/p1/pkgs.osdeps overridden by /opt/workspace/autoproj/p2/pkgs.osdeps:
WARN:   resp. pip: setuptools==40.0.0
WARN:   and   pip: setuptools==41.0.0
WARN: my_package from /opt/workspace/autoproj/p2/packages.autobuild is overridden by the definition in /opt/workspace/autoproj/p1/packages.autobuild

In essence:

• The osdep definition is taken from packge set p2, which is defined second in the buildconf manifest.
• The autobuild package definition is taken from package set p1, which is defined first in the buildconf manifest.

As far as I am aware, this didn't cause any obvious errors for us. But just to be sure: is this the intended behavior?

[doudou]

It is the intended behavior, but I have to admit I never realized it was indeed very confusing.

Fixing it would require breaking backward compatibility.... Not sure what would be the best way forward.

[moooeeeep]

Doesn't this break things if the packages actually require different versions of a dependency?

The package version selected from p1 would be incompatible to the osdep version selected from p2.