[Guidelines Change] Changes to the Packaging Guidelines

Kevin Fenzi kevin at scrye.com
Tue Mar 11 14:31:14 UTC 2014


On Mon, 10 Mar 2014 21:56:13 -0400
Bill Nottingham <notting at splat.cc> wrote:

> Tom Callaway (tcallawa at redhat.com) said: 
> > As part of the ongoing effort to update the guidelines for an
> > eventual change from python2 to python3 as the default python we're
> > promoting use of %{python2}, %{python2_sitelib}, and
> > %{python2_sitearch} instead of the unversioned %{python},
> > %{python_sitelib}, and %{python_sitearch} macros. These macros are
> > not available for EPEL5 and EPEL6. We've updated the Python
> > Guidelines to mention conditionally defining those macros for EPEL5
> > and EPEL6 builds.
> 
> Given that EPEL controls epel-release, and epel-release is in
> @buildsys-build, does it make sense to put macros like this in
> epel-release itself for build uniformity?

It could. We already have some ghc rpm macros in there... 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140311/0f308a6d/attachment.sig>


More information about the devel mailing list