Spec depends on BuildRequires?

Michael Schwendt mschwendt at gmail.com
Tue Mar 11 19:33:31 UTC 2008


On Tue, 11 Mar 2008 14:05:47 -0500, Rex Dieter wrote:

> Michael Schwendt wrote:
> 
> > On Tue, 11 Mar 2008 11:59:34 -0500, Rex Dieter wrote:
> 
> >> spoiler:
> >> (hint: it does and doesn't.  does leave it out at time of srpm
> >> generation, includes it in generating final binary rpm).
> > 
> > At srpm generation the Requires are ignored anyway, because BuildRequires
> > become Requires in the src.rpm.
> 
> Not exactly ignored, but in my experience,
> Requires: <garbage>
> can (sometimes?) induce failures and errors.

Yes, because the .spec parser can run into error conditions, such as empty
Requires lines or invalid expressions due to undefined macros. But that is
exactly why you suggested conditional Requires, which are only evaluated
if certain build requirements are available. 
What I mean is that even a valid unconditional "Requires: foo" tag is never
included in the src.rpm.




More information about the devel mailing list