On 03/27/2012 02:43 PM, Mr Dash Four wrote:
>
>> 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.
>>
> No, no, no!
>
> You don't define any %configure macros at all - they are already
> installed by the distro on your machine - that is the beauty of it all,
> the "%configure" is already there, you don't have to do a thing!
>
> It has all the "default" directories there as determined by that distro
> - being Fedora SUSE etc. As soon as you trigger "%configure" the whole
> lot is completed for you and control is passed to an executable file
> (script) in the BUILD directory.
>
> You read the various parameters there, weed out what you don't need etc
> and write this to shorewall-pkg.config or whatever name you decide to
> use, so that install.sh can pick it up later and do its magic.
>
>> - If you don't like what mine does, you put a %configure in your
>> .rpmmacros file that does things the way that you want.
>>
> Nope! If I would like to change a directory (OK, for the sake of
> argument let's just say it is VARDIR), which is different from the
> "defaults" offered by the "standard" version of "%configure", I define
> my own macro and put these variations there - "%configure" is smart
> enough to pick it up and, again, you don't have to do a thing as the
> whole lot is passed on to BUILD/configure and you take it from there.
> You don't care what the directory name is, as long as it is specified.
>
> My point with the example I have given you in the previous post is that
> if you write your own shorewallrc.%{_vendor} file and include what you
> *think* is the right/standard values of the various directories provided
> by a certain distro, and then proceed to *not* pick up that value from
> "%configure" later on (as is the case with VARDIR - it is missing from
> your original list of directories, right?), then you are not going to
> have the correct value of that directory if:
>
> 1. The distro decided to change that directory recently (say, as a
> matter of policy or other such guff!); or
> 2. I have redefined that directory to what I choose to use on my own
> machine (it is my PC, right?); or
> 3. You've just got it plain wrong as the list of directories you
> included in that shorewallrc.%{_vendor} is your own interpretation of
> these values at the time you created that file and distributed it
>
> So, all I am suggesting to you is this: Just get everything you possibly
> can from %configure" and do *not* introduce any restrictions like you
> did with the list you included in the previous post.
My current configure script has no restrictions.
>
> 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.
-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
