Jeff Johnson wrote:

>> Do we need some pre-defined RPM macro values that
>> contain the file extensions for exe and shlib ?
>>
>> Currently these are usually hardcoded in specs as
>> "" and ".so" respectively, which usually works...
>> (and not applicable to spec files that doesn't use
>> %files for listing names, but instead %files -f)
>
> You mean for building? For installs, file(1) classification
> through libmagic should be more than enough, and the
> mimetypes can be easily added to *.rpm whenever (I've asked
> whether there is interest several times now, not heard any
> interest yet).

I meant for building, yes.

> There's certainly nothing stopping anyone from creating
> their own macros to produce *.rpm packaging however they wish.

Nope, and they have done so. To each and every spec file.

> Adding as "default" to rpm is tricky only because of lack
> of consensus: the NAY's invariably outnumber the YEA's
> these days.
>
> But feel free to do whatever. Real Soon Now macro configuration
> needs to be refactored and reorganized into smaller and more 
> specifically
> targeted configuration. One build macro more or less simply does not 
> matter.

Added all four of them...

--anders