Filtering requires/provides

[Steven Pritchard]

On Wed, Mar 08, 2006 at 02:10:12PM -0600, Jason L Tibbitts III wrote:
> So where are we at?  We can't mess with buildroot (because the
> module's signing stuff will complain) and we can't mess with
> sourcedir.  How about just making another directory:
> 
> %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)-blah
> 
> emitting the script there (or copying it through sed to do the
> expansion) and then cleaning it up in %clean?

I think I like that.  It's not too ugly, and it satisfies all of my
concerns.

We add this:

  Source1:        filter-requires.sh
  %global real_perl_requires %{__perl_requires}
  %define __perl_requires %%{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n)-filter-requires

Then in %prep do this:

  sed -e 's,@@PERL_REQ@@,%{real_perl_requires},' %{SOURCE1} > %{__perl_requires}
  chmod +x %{__perl_requires}

And make %clean this:

  rm -rf $RPM_BUILD_ROOT %{__perl_requires}

I've updated the perl-Kwiki-Raw spec to use this instead.

Steve
-- 
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve at kspei.com             http://www.kspei.com/
Phone: (618)398-3000               Mobile: (618)567-7320