Re: [opensuse-packaging] How to check for unneeded build requirements?

On Montag, 15. Februar 2016, 09:30:53 CET wrote Andrei Borzenkov:

On Mon, Feb 15, 2016 at 9:15 AM, Dave Plater wrote:

...

On 14/02/2016 21:25, Roman Evstifeev wrote:

...

Hi. Is there any way to know if a "BuildRequires" in my spec file was not used in build process?

Not as far as I know. The README or INSTALL file in the sources will normally list the build dependencies otherwise you can try commenting out the BuildRequires: and see the output of configure. Configure / cmake output normally lists everything that it searches for but sometimes you might just get a build failure due to a missing header.

The problem is that quite often you will not get failures but some features will be silently omitted. So package will build, but with reduced functionality. In the best case this will cause some files to be missing, but if package is using wildcards or does not create additional binaries, all bets are off.

Another way to detect this is to diff the "rpm -qp --requires $rpm" built with and without the buildrequires. At least if the build requires is a library the chances are high that you see that in the requires list. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org