SCIENTIFIC-LINUX-DEVEL Archives

August 2015

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux developers worldwide <[log in to unmask]>
Date:
Thu, 6 Aug 2015 15:37:34 +0200
Reply-To:
Paul Millar <[log in to unmask]>
Message-ID:
Content-Transfer-Encoding:
7bit
Subject:
From:
Paul Millar <[log in to unmask]>
Content-Type:
text/plain; charset="windows-1252"; format=flowed
In-Reply-To:
MIME-Version:
1.0
Comments:
To: Pat Riehecky <[log in to unmask]>
Parts/Attachments:
text/plain (27 lines)
Hi Pat,

On 06/08/15 15:01, Pat Riehecky wrote:
> This looks like the same behavior noted in:
> https://bugzilla.redhat.com/show_bug.cgi?id=594672

Yes, I think this is the underlying cause.

This "well known" feature of RPM (that macros are expanded, even when 
commented out) wasn't known to me.  It is also inconsistently 
documented; c.f.
	http://www.rpm.org/max-rpm/ch-rpm-specref.html
and
	http://www.rpm.org/max-rpm-snapshot/ch-rpm-specref.html

[Unfortunately, it seems nearly impossible to report this inconsistency 
to whoever maintains the Max RPM documentation, so the incorrect 
documentation will likely linger, *sigh*]

That all said, given how macros are expanded, I think it's fair to say 
that the previous successful builds worked-by-accident, and there is no 
regression.

Sorry for the noise.

Paul.

ATOM RSS1 RSS2