Re: spec file for multiple distributions.

[John Pye <john pye student unsw edu au>]

Hi Tony,

Tony Earnshaw wrote:
> John Pye skrev, on 05/21/2007 09:27 AM:
>
>> Tony Earnshaw wrote:
>>>>  use %{dist} but it's defined in a macro? and about naming
>>>> packages : can i dynamically name a package regarding to the
>>>> distribution it's been built ?
>
>
> I never wrote that ...

It was from the original poster. Bad '>>' quoting on my part, sorry.

>
>> %{dist} can be defined in your .rpmmacros file, which you create in your
>> home directory on each separate build host. Then you add %{dist} at the
>> end of your 'Release:' line, and the .rpm files will end up with the
>> dist tag in the resulting filenames (suggest that you use %{?dist} so
>> that if the marco file is missing, you end up with no text added).
>
> This advice has the ovious disadvantage that it presupposes that
> *everbody* has this definition in their .rpmmacros file - even that
> they have an .rpmmacros file at all. Most people don't. Most of the
> grown-up spec writers I know have some method of defining %dist in
> their spec files, too many to name.

One can use the %{?dist} syntax, can one not? Then if the macro is not
defined, the resulting RPM is simply without a distro-specific filename.
As a juvenile spec-writer I have found this to be reasonably satisfying :-)

As here:
http://ascendcode.cheme.cmu.edu/viewvc.cgi/code/branches/extfn/ascend.spec?revision=1630&view=markup

Cheers
JP


-- 
John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia
http://pye.dyndns.org/