> My current configure script has no restrictions.
>
Good, though I thought you are only going to honour a subset of the
variables that could be defined in those shorewallrc.%{_vendor} files,
in which case if I use %configure to pass something extra (via my own
rpm macro or just adding an extra parameter to the %configure line in my
.spec file) this will not be honoured.
If that is not the case and your configure script file does not have any
restrictions, then all this is a storm in a teacup!
>
>> By all means, honour your original shorewallrc.%{_vendor} values, but
>> let these get overwritten by %configure (*without* restrictions!) - that
>> is simply what I have tried to illustrate with my previous post. it is
>> really that simple! Do you understand it now?
>>
>
> Sorry -- I'm a virtual rpm illiterate. If you want to override something
> (say VARDIR for which there appears to be no standard RPM macro), how
> are you going to do that? I'm obviously missing something.
>
I have the precise statement on one of the dev machines at home and
could post later it if you are interested - let me know.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
