You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current release bootstrap Autoproj.manifest.main_package_set is available while the init.rb of the package set is run. With the dev bootstrap nil is returned in the package set. It is later available in the overrides.rb of the buildconf though.
The interesting part of the output:
Release version:
p1/init.rb: is good
buildconf/overrides: is good
Dev version:
p1/init.rb: is nil
buildconf/overrides: is good
Not sure if this is some internal API which is subject to change without notice. But one of our package sets appears to use it, which is now broken with the dev version.
The text was updated successfully, but these errors were encountered:
We've stumbled accross another inconsistency between the behavior of the current release version (2.15) and current master.
Consider this buildconf: https://github.com/moooeeeep/buildconf_3
With the current release bootstrap
Autoproj.manifest.main_package_set
is available while theinit.rb
of the package set is run. With the dev bootstrapnil
is returned in the package set. It is later available in theoverrides.rb
of the buildconf though.The interesting part of the output:
Release version:
Dev version:
Not sure if this is some internal API which is subject to change without notice. But one of our package sets appears to use it, which is now broken with the dev version.
The text was updated successfully, but these errors were encountered: