On Thu, Aug 18, 2011 at 3:42 PM, Iain Arnell <iarnell@xxxxxxxxx> wrote:
> On Thu, Aug 18, 2011 at 3:22 PM, Jon Ciesla <limb@xxxxxxxxxxxx> wrote:
>> I do some macro gymnastics with vym to prevent it Requiring a perl module
>> that's named one thing in SuSE and another in Fedora. With my latest f17
>> build, that stopped working, while builds of the same code and spec on f15
>> and f16 seem to be ok. Did rpm's behaviour change?
>
> The perl_default_filter macro changed with perl 5.14. We're now using
> rpm's native __requires_exclude macro (and friends) instead of the
> slightly hacky filter_setup stuff. Ideally, we'd drop the
> filter_setup/filter_from_requires entirely, but to keep a single spec
> compatible with all current fedora branches, you can do:
>
> --- vym.spec.orig 2011-07-20 19:58:57.000000000 +0200
> +++ vym.spec 2011-08-18 15:37:06.427529132 +0200
> @@ -22,6 +22,7 @@
> %filter_from_requires /^perl(BugzillaClient)$/d
> %?perl_default_filter
> }
> +%global __requires_exclude
> %{?__requires_exclude:%__requires_exclude|}perl\\(BugzillaClient\\)
^ That should be one line, of course.
And I noticed that you already have a __requires_exclude. But at the
minute, it *must* come after perl_default_filter.
--
Iain.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
