According to <a href="file:///usr/share/doc/rpm-4.0.4/apidocs/tsort.html">file:///usr/share/doc/rpm-4.0.4/apidocs/tsort.html</a> rpm allows BuildRequires-specialization for sections. I suggest to use it in the output of buildreq. I have a reason for this: now, when BuildRequires are not specialized, rpmbuild often doesn\'t want to proceed with some action like \"--clean\" because some of the BuildRequires are not there. This is inconvenient because in most cases the packages listed in BuildRequires are not really required for %clean or a certain other action. I suggest that buildreq generates three kinds of build-dependencies: first, it traces something like \'rpmbuild -bE\' and sees what is required to preprocess the spec; these dependencies are written as BuildPreReq. Then it traces %prep and writes BuildRequires(prep) and then it traces %build and writes BuiildRequires(build). --- --- 0.4.4-alt1
Isn't it better to fix --clean? The thing is, rpmbuild -bs usually won't need BuildRequires either (might need BuildPreReq though) and still one would cope with --nodeps just to wrap up an srpm.
Предложение опирается на секционные BuildRequires(prep)/(build) из документации rpm 4.0.4 (doc/manual/tsort). В коде rpm 4.13.0.1 в Сизифе этих флагов нет: build/parsePreamble.c знает только pre/post/preun/postun/verify, RPMSENSE_SCRIPT_PREP/BUILD/INSTALL/CLEAN остались лишь в старом документе; в апстримном rpm их тоже нет. buildreq не может генерировать то, что rpmbuild не умеет проверять. Исходная мотивация (rpmbuild --clean требует все BuildRequires) решается ключом --nodeps, а сборка в hasher ставит весь список целиком. Закрываю как WONTFIX.
