> 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}
>
How do you know the rest of the directories won't change? Also, how do
you know I am not using, for example, a different VARDIR (specified in a
separate rpm macro so that %configure picks it up), which points to a
permanent storage/read-write partition, let alone the case when I might
be using different PREFIX?
I think you should get as much as possible from %configure and leave it
at that.
Fair enough, you discard .shorewallrc - makes sense since I am going to
build a package, but I think "configure" (the script) should squeeze as
much as possible from "%configure". I am also assuming that when
%configure is executed the %{_vendor} parameter would be passed as well,
is that so?
------------------------------------------------------------------------------
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
