Bug 1099 - more specialized BuildRequires
Summary: more specialized BuildRequires
Status: NEW
Alias: None
Product: Sisyphus
Classification: Development
Component: rpm-utils (show other bugs)
Version: unstable
Hardware: all Linux
: P4 enhancement
Assignee: Nobody's working on this, feel free to take it
QA Contact: qa-sisyphus
Depends on:
Reported: 2002-07-15 12:36 MSD by imz
Modified: 2014-12-20 16:27 MSK (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description imz 2002-07-15 12:36:03 MSD
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 \&quot;--clean\&quot; 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).


Comment 1 Michael Shigorin 2010-10-09 19:01:36 MSD
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.