Filtering requires/provides

[Ville Skyttä]

On Wed, 2006-03-08 at 14:49 -0600, Steven Pritchard wrote:
> 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.

I don't quite understand what makes writing an external script and then
modifying it from the specfile better than just emitting the script
completely from the .spec in %prep, given that the script will usually
be just a few lines.

>   Source1:        filter-requires.sh

For a guideline, that's a too generic filename.
%{name}-filter-requires.sh would be better.

>   %define __perl_requires %%{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n)-filter-requires

Could possibly use %define __perl_requires %{buildroot}-filter-requires
(untested).  The double %% appears to be a typo.