so the question is then do we need to run this all the time or is it good enough during the dev phase of the package - i.e. in the devel project.

This we could easily achieve with

%bcond_with makedepends
…
%if %{with makedepends}
BuildRequires: makedepend
%endif
…
%build
…
%if %{with makedepends}
make depend
%endif
…

and defining _with_makedepends 1 in prjconf of the devel project.

Then devel would make use of this dep tracker and give you the hints, without costing extra on the actual distro.

This of course is only really viable if issues mostly come from ncurses changes, and not from whatever other package changes might cause

Dr. Werner Fink (WernerFink) - over 3 years ago

source maintainer

I had seen random errors on builds ... what I do not understand: why does a simple dependency tool cause such an overhead.

Dominique Leuenberger (dimstar) - over 3 years ago

reviewer

Ring0 is the bare minimum I need to copy binaries around and in sycn to get the distro going - for hopefully obvious reasons, I want to keep that as possible, not blowing it up more than is really nescessary

ncurses is part of that ring0 bootstrap cycle already - so new deps it wants to pull in need some thoughts