> 1. Retain the shorewallrc.* files. They will provide default values.
>
> 2. Use a variation of Mr Dash Four's configure script. The config file
> it builds will use the settings in shorewallrc.%{_vendor} as
> defaults and override directory settings from rpmmacros. That is
> necessary because the installers need information
> that isn't known to rpm.
>
Am I right in thinking that the order in which various directories get
pulled/set is as follows:
1. shorewallrc.%{_vendor} file in the source directory
2. .shorewallrc (installed in one of the 5 possible places on the BUILD
system)
3. "%configure" + various additional parameters specified when this file
is executed (this gets set in shorewall-pkg.config)
So, that would mean whatever is set via
"%configure"/shorewall-pkg.config takes presedence.
------------------------------------------------------------------------------
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
