On Mon, Aug 15, 2016 at 2:40 PM, Dave Johansen <davejohansen@xxxxxxxxx> wrote: > On Mon, Aug 15, 2016 at 12:24 PM, Tom Callaway <tcallawa@xxxxxxxxxx> wrote: >> >> Recently, I've been participating in some discussion as to how to enable >> C++11 support for EPEL builds. Specifically, R (and its large universe >> of addons in CRAN) would benefit significantly from C++11 support. >> >> After much discussion, it seems like the only sane way to do this is to >> use the Red Hat Developer Toolset (for el6 and el7). It is my >> understanding that all RHEL customers (and CentOS users) should be able >> to enable this repository without restrictions. >> >> I'd like to propose that we enable the Developer Toolset repo in EPEL >> and allow packages to depend on it. Thoughts? > > > Previously, the big hold up was that it was at least partially behind a > paywall, but now that it's open and headed up by a SIG, I don't see any > reason why we shouldn't start benefit from using it. It might be nice to > have some rules or at least recommendations on which version to use and > there will need to be a policy when versions are EOLed, but maybe just an > automated set of rebuilds would be sufficient. Probably the best way to do this would be to create a "wrapper" package that would point to the latest version and provide a macro for setting up the environment so that the spec uses the Developer Toolset compiler for building the software instead of the system one. Maybe "devtoolset-toolchain" or something like that? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ epel-devel mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
