On Thu, Sep 19, 2013 at 12:18 PM, Dave Johansen <davejohansen(a)gmail.com> wrote:
On Thu, Sep 19, 2013 at 10:47 AM, Ralf Corsepius
> Correct me if I am wrong, but to my knowledge, RH's devtoolset is only
> available to RH customers, which would mean EPEL can not use it.
Yes, the devtoolset requires the appropriate subscription from RH, but that
is the point of my request. I would like to request that devtoolset be made
available on Koji so it can be used to build certain packages. The 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 devtoolset installed, so it
doesn't violate any of the RH/EPEL policies, but would enable the use of the
devtoolset with the EPEL.
This is a bit of a tangent from the comments on the packaging
guideline draft but in addition to Fedora passing draft guidelines,
needing a separate subscription from RH may run afoul of a different
EPEL Guideline -- the packages that EPEL bases against are not all of
RHEL but only ones that come/came with the base subscription. This is
a little ambiguous because this was figured out in the RHEL5 times but
RHEL6 has slightly different subscriptions/channels/what have you. I'm
not sure if the devtoolset you talk about will be a part of that or
not. If it isn't you (or someone) would need to package those up for
EPEL before they could be used to build other packages.
Do note that pulling the devtoolset into EPEL's buildroot directly
from RedHat isn't something that we'd decide upon in the Fedora
Packaging Committee. EPEL people sent you here because what we (FPC)
decide about SCLs in Fedora will inform their views on whether and how
EPEL should implement SCLs. So they're waiting on us but their
decisions will be separate.