On Wed, May 13, 2015 at 10:07 AM, Colin Walters <walters(a)verbum.org> wrote:
On Wed, May 13, 2015, at 10:02 AM, Dennis Gilmore wrote:
> This is a big part of why we need it integrated into the tooling. we can
> define a pungi config that has a subset of the full compose, i.e. the atomic,
> and possibly cloud and/or livecd bits. we can then make them as part of the
> updates push process and promote them to stable at any time.
That sounds reasonable offhand...but there's a lot of important details, such
as whether or not the cloud image is part of it.
> not at all. the same tooling will work for CentOS, and RHEL.
There's no python3/dnf in CentOS7, right? Or were you thinking those
would be maintained in infrastructure repos/EPEL?
Python3 specifically is being worked on for EPEL7[0][1] for various
reasons, Infrastructure and Rel-Eng included. I'm not sure dnf is
needed as a requirement, but it is in EPEL7[2] already if that becomes
necessary.
-AdamM
[0] -
https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3
[1] -
https://bugzilla.redhat.com/show_bug.cgi?id=1219411
[2] -
http://dl.fedoraproject.org/pub/epel/7/x86_64/repoview/dnf.html
_______________________________________________
rel-eng mailing list
rel-eng(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/rel-eng