Jeff Johnson wrote:
> 
> On May 7, 2009, at 10:55 AM, Mark Hatle wrote:
> 
>> Ok.. I understand now.. then my suggestion is that these should be 
>> macros so that individual distributions can set specific 
>> initialization options.  A reasonable default macro should be provided 
>> as well.
>>
> 
> Look, you will get a macro, likely with colon separation for multiple
> paths, and globbing, and URI's, and security checks with digital
> signatures/digests as well as simple owner/permission checks ...

Macros I was referring to are the __build_pre, __build_post and similar.  This 
style would allow basic initialization sequences such as the example you provided:

use strict;
use IO::String;
our $io = IO::String->new;
select $io;
use RPM;

I'm not sure anyone is going to be able to provide a definitive answer as to 
what text everyone wants to use.. so pick a default, pick a way for distros to 
customize and make the assumption nobody will.. ;)

--Mark

> ... BUT ...
> 
> I need consensus on what path to use in order
> to proceed to the rest.
> 
>> (In many ways I equate this to the various pre/post-prep, build, and 
>> install macros that already exist.)
>>
> 
> Well, none of those are macros, they are all spec file section markers,
> for starters.
> 
> 73 de Jeff
> 
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> Developer Communication List                        rpm-devel@rpm5.org