Tom "spot" Callaway wrote: > On 01/31/2018 10:53 AM, Stephen John Smoogen wrote: >> So we have a problem with what is the canonical place for SCL's. I was >> going from http://mirror.centos.org/centos/7/sclo/ which just says x86_64. > > Even just getting x86_64 devtoolset into the potential buildroot for > EPEL would be hugely helpful to me, because that's all chromium cares > about right now. I filed a pull request to update mock-core-configs: https://github.com/rpm-software-management/mock/pull/159 If anyone here knows relevant folks on the SCL team who can provide some input on the preferred/canonical repository URLs (or any other issues with that PR), it would be great. I tend to think that the mock configs we ship should use whatever URLs the centos-release-scl{,-rh} packages use. That's what end-users would see if they wanted to rebuild packages outside of mock. If those change we can always update them in mock-core-configs to match. -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Health is merely the slowest possible rate at which one can die.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
