Re: Additional python34 components for epel7
So what should package maintainers do? I modified a package to use python3_pkgversion and it builds fine if with_python3 is set, but it doesn't seem to be set in the EPEL 7 build environment. I noticed a couple packages enable it by default. Is that what we should be doing? Or should we just build it into python/python3_epel7 in copr for now, and it so how? Avram On Mon, Jan 4, 2016 at 2:08 PM, Jason L Tibbitts III wrote: > > "DF" == Denis Fateyev writes: > > DF> If we just could work "the same SRPMS name" problem around ;-) > DF> Healthy repos with the master branch orphaned [1] may look a little > DF> weird to users... > > That is not abnormal for EPEL-only packages, though. The dead.package > file in master should simply indicate that the package is EPEL-only. > > - J< > ___ > python-devel mailing list > python-devel@lists.fedoraproject.org > > http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org > ___ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
Re: Additional python34 components for epel7
On 01/19/2016 05:30 AM, Avram Lubkin wrote: So what should package maintainers do? I modified a package to use python3_pkgversion and it builds fine if with_python3 is set, but it doesn't seem to be set in the EPEL 7 build environment. I noticed a couple packages enable it by default. Is that what we should be doing? Or should we just build it into python/python3_epel7 in copr for now, and it so how? with_python3 is purely an individual python package setting - the build system does not set that. So you should enable it if you want. The copr is just for testing new packages. Any member of the python sig FAS group should be able to submit builds there. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
unsubscribe
unsubscribe ___ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
unsubscribe
unsubscribe ___ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
Re: Additional python34 components for epel7
2016-01-19 16:18 GMT+01:00 Orion Poplawski : > On 01/19/2016 05:30 AM, Avram Lubkin wrote: >> >> So what should package maintainers do? I modified a package to use >> python3_pkgversion and it builds fine if with_python3 is set, but it >> doesn't seem to be set in the EPEL 7 build environment. I noticed a >> couple packages enable it by default. Is that what we should be doing? >> Or should we just build it into python/python3_epel7 in copr for now, >> and it so how? > > > with_python3 is purely an individual python package setting - the build > system does not set that. So you should enable it if you want. > Just thinking aloud but to encourage reuse of spec files between CentOS (which has no python34) and EPEL, it would be nice to keep the with_python3 boolean and test both %epel and %fedora macros definition rather than just dropping the setting. H. > The copr is just for testing new packages. Any member of the python sig FAS > group should be able to submit builds there. > > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA/CoRA DivisionFAX: 303-415-9702 > 3380 Mitchell Lane or...@cora.nwra.com > Boulder, CO 80301 http://www.cora.nwra.com > > ___ > python-devel mailing list > python-devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org ___ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
