On Fri, Sep 20, 2013 at 8:44 PM, T.C. Hollingsworth <
On Fri, Sep 20, 2013 at 2:23 PM, Dave Johansen
> Part of the confusion may also come from the fact that the binaries
> generated by devtoolset are standalone and can be run on vanilla
> RHEL 5/6 (i.e. without the devtoolset installed). So generally the
> devtoolset is only needed during build time, but since the ODB compiler
> plugin for gcc, the devtoolset is required for it's use when generated
> for use with the runtime.
> In summary, the devtoolset requires the appropriate subscription from RH,
> but that is the point of my request. I would like to request that
> be made available on Koji so it can be used to build certain packages.
> idea is that then it will build the rpm on the server and it will be
> available in the EPEL (but not the devtoolset itself). This means that
> anyone who would want to use this package would need to have the
> installed, so it doesn't violate any of the RH/EPEL policies, but would
> enable the use of the devtoolset with the EPEL.
As you indicated in the other thread, the devtoolset channel is only
developer RHEL subscriptions. I'd presume the vast majority of EPEL
have server-type subscriptions, so they wouldn't have access to it,
That kind of sucks—there would be packages in EPEL that would have broken
for a lot of EPEL users and no real way of indicating to those users what
problem is. :-(
What about CentOS and Scientific Linux? These are 100% fully supported
for EPEL  and cannot be ignored. If they have no access to it, it
be used in EPEL. On the other hand, if most of those users have access to
necessary dependencies, it might lessen the severity of lack of access to
fide RHEL users in some peoples' eyes.
There are rebuilds of devtoolset by both the CentOS and Scientific Linux
guys. It obviously comes without the support that you get with the RedHat
subscription, but it's still an option and is available to anyone (not just
the CentOS or Scientific Linux guys). The repos can be found at:
In general, it seems your package is much more suited for a
similar. It doesn't seem to be generally useful to the vast majority of
consumers, just to users with a very limited set of RHEL subscriptions.
the point of making something available in EPEL if the vast majority of
users can't use it?
I don't really get this line of reasoning. Is "generally useful" now a
requirement to be part of the EPEL? I've always had the understanding that
if it's useful to someone on RHEL, they're willing to maintain it, and it
makes it through the approval process, then it's ok to include in the EPEL.
I recognize that RedHat has made the use of the devtoolset unnecessarily
complex because of the additional subscription that's required, but that's
why I want to start this discussion. I'd like to help the community figure
out how to make use of this very useful tool (the devtoolset) and be able
to add to the excellent set of packages that the EPEL already is.