On 03/27/2012 09:11 AM, Mr Dash Four wrote:
>
>> 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?So let me see if I understand the big picture. - I have a %configure macro defined in my .rpmmacros that does what I want it to. - If you don't like what mine does, you put a %configure in your .rpmmacros file that does things the way that you want. If this is what you are proposing, then do you believe that I should publish my own %configure in some form so you and other RPM builders can hack it to suit your needs? -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
