On 12/30/2015 02:48 PM, Neal Gompa wrote:
On Wed, Dec 30, 2015 at 3:46 PM, Orion Poplawski
<orion(a)cora.nwra.com> wrote:
> I've submitted a review for a separate python-macros package here:
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=1294904
>
> This is what the FPC approved here
>
https://fedorahosted.org/fpc/ticket/567#comment:12 to be added to the Fedora
> buildroots to provide the %python3_pkgversion macro needed for compatibility
> with the EPEL Python3 packaging guidelines.
>
> It also serves the much more important goal of getting the python macros out
> of the the individual python? packages to make it easier to update them.
>
Don't we normally name these something to the effect of
"<name>-srpm-macros"? For example, we have "go-srpm-macros"
and
"perl-srpm-macros". Shouldn't this be named "python-srpm-macros"
for
consistency purposes?
How does this seem:
Spec URL:
http://www.cora.nwra.com/~orion/fedora/python-rpm-macros.spec
SRPM URL:
http://www.cora.nwra.com/~orion/fedora/python-rpm-macros-3-2.el7.src.rpm
Combined package, adds:
python-srpm-macros - RPM macros for building Python source packages
python2-macros - RPM macros for building Python 2 packages
python3-macros - RPM macros for building Python 3 packages
python-srpm-macros would be required by redhat-rpm-config. python2-devel
would require python-macros and python2-macros. python3-devel would requires
python-macros and python3-macros.
Main python2/3 package maintainers please chime in.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
http://www.nwra.com