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
If a package is selected for build and one of its dependencies is missing, autoproj will:
Checkout and build the missing dependency if that is a source package;
Do nothing if that is an osdep (the build will most likely fail in this case)
For a more consistent behavior, autoproj should perform an osdeps operation on the packages that are selected for build (this would be disabled by --no-deps/--deps=f).
The text was updated successfully, but these errors were encountered:
I'm not necessarily against this, but only if it is disabled by default and can optionally be enabled.
The problem is that most osdeps are slow, so that would have a non-negligible impact on the build times. If you don't like the inconsistency, then I would simply make build fail even in the source package case, and ask to explicitely run an update.
I guess there will be some impact on build times indeed.. I will do some testing to see how big they are, maybe it doesn't make sense to have this even as an optional feature.
I would simply make build fail even in the source package case
Not sure.. This is a major change in behavior IMO, I don't know how everyone else would feel about that
If a package is selected for build and one of its dependencies is missing, autoproj will:
For a more consistent behavior, autoproj should perform an osdeps operation on the packages that are selected for build (this would be disabled by
--no-deps
/--deps=f
).The text was updated successfully, but these errors were encountered: