Re: Additional python34 components for epel7

[Avram Lubkin]

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 <tibbs(a)math.uh.edu&gt;
wrote:

>  >>>>> "DF" == Denis Fateyev
> <denis(a)fateyev.com&gt; 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(a)lists.fedoraproject.org
>
>  http://lists.fedoraproject.org/admin/lists/[e-mail]...
>