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
My expectation would be that pkg.depends_on behaves as if the package would have DEPEDENCY set in the packages manifest by:
<dependpackage="DEPENDENCY" />
This includes that the override would apply for both, the dependencies in the manifest and the depends_on dependency.
It seem that this is not the case:
When using pkg.depends_on "DEPENDENCY" the override is not applied which leads to an installation of the os dependency anyways. But when listed in the same way via manifest.xml it works.
The text was updated successfully, but these errors were encountered:
When defining a package in the *.autobuild file of a package set it is possible to define dependencies by using:
It is also possible to override os dependencies using source packages by adding the following to the overrides.rb of the package_set.
My expectation would be that pkg.depends_on behaves as if the package would have DEPEDENCY set in the packages manifest by:
This includes that the override would apply for both, the dependencies in the manifest and the depends_on dependency.
It seem that this is not the case:
When using pkg.depends_on "DEPENDENCY" the override is not applied which leads to an installation of the os dependency anyways. But when listed in the same way via manifest.xml it works.
The text was updated successfully, but these errors were encountered: