On Apr 27, 2014 9:37 AM, "Aaron Knister" <aaron.knis...@gmail.com> wrote: > > > On Apr 26, 2014, at 8:58 PM, Toshio Kuratomi <a.bad...@gmail.com> wrote: > >> >> On Apr 26, 2014 8:27 PM, "Aaron Knister" <aaron.knis...@gmail.com> wrote: >> > >> > We use both EPEL and SCL in my org. I didn't see this addressed in the email chain but I'm concerned about what'll happen if/when SCL includes python34. There are technical means to work around this but it fundamentally makes EPEL and SCL incompatible. I don't believe SCL is considered a layered product but maybe I'm wrong :) >> >> If red hat does the right thing and namespaces their scl packages then there shouldn't be any conflicts. Scls are intended to be isolated from system packages while epel packages are intended to integrate into the system. >> >> -Toshio > > The contents are namespaced but the package names are not. We'll end up with a package called python34 in each repo that are incompatible.
Exactly. That's why red hat has to do the right thing. -Toshio
_______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
