proper way to distinguish epel from fedora

Toshio Kuratomi a.badger at gmail.com
Wed Nov 11 15:57:26 UTC 2009


On Wed, Nov 11, 2009 at 12:45:55PM +0100, Farkas Levente wrote:
> On 11/11/2009 10:58 AM, Manuel Wolfshant wrote:
> > Farkas Levente wrote:
> >> On 11/11/2009 05:13 AM, Dennis Gilmore wrote:
> >>  
> >>> On Tuesday 10 November 2009 08:15:58 pm BJ Dierkes wrote:
> >>>    
> >>>> On Nov 10, 2009, at 9:56 AM, Steve Traylen wrote:
> >>>>      
> >>>>> On Tue, Nov 10, 2009 at 4:51 PM, Manuel Wolfshant
> >>>>>
> >>>>> <wolfy at nobugconsulting.ro> wrote:
> >>>>>        
> >>>>>> Farkas Levente wrote:
> >>>>>>          
> >>>>>>> hi,
> >>>>>>> what's the proper way to distinguish epel from fedora in the spec
> >>>>>>> file?
> >>>>>>> i'd like to add
> >>>>>>> ExcludeArch:    ppc ppc64
> >>>>>>> on epel but not in case of fedora in a package (since there is no
> >>>>>>> java
> >>>>>>> on ppc on epel). but what's the current recommended way to do so?
> >>>>>>> unfortunately %{?rhel} is not defined even in rhel-5 so what else
> >>>>>>> can i
> >>>>>>>             
> >>>> Is there any problem with:
> >>>>
> >>>> %if %{el5}
> >>>> ExcludeArch: ppc ppc64
> >>>> %endif
> >>>>       
> >>> yes nothing defines %{el5}  and you would get a failure on all targets
> >>> the correct way to handle it would be
> >>> %if 0%{?rhel} > 1
> >>> ExcludeArch: ppc ppc64
> >>> %endif
> >>>     
> >>
> >> which is still not working for those who not install the extra packages
> >> buildsys-macros and of course won't work with rhel 6 where these exclude
> >> shouldn't have to defined.
> >> so until now no one send a general good solution:-(
> >>
> >>   
> > The mock rpm distributed in epel contains something similar to
> > 
> >    [groups]
> >    name=groups
> >    baseurl=http://buildsys.fedoraproject.org/buildgroups/rhel5/x86_64/
> > 
> > I do not want to sound harsh but if you refuse to use the macros which
> > define the settings of the build infrastructure (either passing the info
> > to mock or by defining  it in .rpmmacros (or any similar way)), how do
> > you expect to find out what distro you are building for ?
> 
> the difference is that on fedora the distro itself contains these macro
> while on rhel it's an external addon package.
> 
Note: You can also check for the absence of %{fedora} macros in cases where
no RHEL release will support the feature.

So:

%if 0%{?fedora} < 1
ExcludeArch: ppc ppc64
%endif

When RHEL6 comes out you'll need to update the macro but -- it could be that
there still won't be the needed support on ppc or it could be that RHEL6
defines the %rhel macros so it might not be an issue.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20091111/a2b42274/attachment.sig>


More information about the epel-devel mailing list