On 03/27/2012 08:16 AM, Mr Dash Four wrote:
>
>> 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)
When building an RPM, I propose a simple two-tier scheme.
- Default settings are established via shorewallrc.%{_vendor}
- %configure overrides the following settings from that file:
SBINDIR - from %{_sbindir}
SHAREDIR - from %{_datadir}
MANDIR - from %{_mandir}
CONFDIR - from %{_sysconfdir}
LIBEXECDIR - from %{_libexecdir}
PERLLIBDIR - from %{perl_privlib}
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
