On Tue, 23 Aug 2016 14:21:24 +0100 Karanbir Singh <mail-lists@xxxxxxxxx> wrote: > On 22/08/16 18:30, Jason L Tibbitts III wrote: > >>>>>> "DJ" == Dave Johansen <davejohansen@xxxxxxxxx> writes: > > > > DJ> devtoolset is designed to do all of this and is already done, > > DJ> so it seems that the only advantage to putting it in EPEL > > DJ> itself would be to reduce the number of repos during build > > DJ> time. > > > > So is devtoolset something I get access to as a CentOS user? How > > do I build these packages myself (i.e. in mock)? > > you should be able to 'yum install centos-release-scl' on a CentOS > Linux machine and get access to all the SCLs Yeah, but if we enable that for EPEL builds, we are going to get all SCLs right? So, people could start depending on them at runtime instead of just install time. I'm not opposed to devtoolset, but I don't think we want to allow runtime scls without actual scl guidelines. kevin
Attachment:
pgpmIcmB3Yzjy.pgp
Description: OpenPGP digital signature
_______________________________________________ epel-devel mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
