I think it's poor form to make some random macro package a
requirement to rebuild an RPM.
I did just discover the %{expand: } macro (which is amazingly
undocumented), which seems to almost do what I want, but it's
ignoring conditionals, which seems to be a known issue, based on a
post to the list in December '03.
So if anyone can provide insight on how to workaround %expand's
failing to parse conditions, that would be great, or if there's some
analog to %expand which does an actual 'eval' instead of parsing line
by line.
-Jon
On Jul 13, 2006, at 12:41 PM, Matthew Miller wrote:
On Thu, Jul 13, 2006 at 12:35:06PM -0400, Jonathan Reed wrote:
Because I want the spec file which ends up in the SRPM to have those
platform detection macros.
BuildRequires: jonathans-package-detectionmacros-rpm-config
?
--
Matthew Miller mattdm@xxxxxxxxxx <http://
mattdm.org/>
Boston University Linux ------> <http://
linux.bu.edu/>
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
