On Jul 30, 2008, at 5:50 AM, Ralf S. Engelschall wrote:

> On Wed, Jul 30, 2008, Jeff Johnson wrote:
>
>> This "band-aid" prevents installing argv.h in /usr/include/rpm w/o  
>> messy
>> AutoFu.
>
> Really? If no Autoconf #defines are present, _nothing_ happens. The
> stuff degrades gracefully to just no #include at all. So, this should
> not cause any problems.
>

And the degradation was the problem that arekm set out to solve.

The AutoFu imposes conventions on using rpm include files.

Imposing conventions is no different than asking applications to do
     #include <stdint.h>
or whatever else is necessary to supply typedefs.

>> All rpm include files should __NOT__ carry AutoFu #defines into /usr/
>> include.
>>
>> Automagically including <stdint.h> is far worse than just forcing
>> applications to
>> include <stdint.h> (or inttypes.h or using their own typedefs's or
>> whatever)
>>
>> Is it __REALLY_ that hard to get application developers to add
>>    #include <stdint.h>
>> where needed?
>
> Well, it was not my idea to include <stdint.h> there. I just wanted to
> fix the build-time problems the new addition of <stdint.h> caused. I'm
> happy to leave out everything (the status-quo as before <stdint.h> was
> added), but I can also live with the current band-aid as it at least
> degrades gracefully IMHO.
>

Yes it degrades gracefully to no include at all.

Which was the problem that arekm set out to solve.

sizeof(int) == 4 on all platforms of interest afaik.

Private int typedefs, instead of stdint.h include, are at least self- 
consistent,
no "degraded" behavior, less complex, and otherwise pleasing.

Alternatively, all includes can be expanded, with helper includes  
directly
inserted before install into /usr/include/rpm. But let's not go  
there ...

73 de Jeff
>                                        Ralf S. Engelschall
>                                        rse@engelschall.com
>                                        www.engelschall.com
>
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> Developer Communication List                        rpm-devel@rpm5.org