On 27 January 2018 at 18:45, Todd Zullinger <[email protected]> wrote:

> Stephen John Smoogen wrote:
> > On 27 January 2018 at 15:41, Todd Zullinger <[email protected]> wrote:
> >> I'm not sure if we want to limit the package set to
> >> devtoolset* via includepkgs or not.  I did so in the above
> >> commit and have tested it very lightly.  Restricting the
> >> packages may help prevent packages from accidentally pulling
> >> in bits from SCLo beyond the intended devtoolset packages.
> >>
> > If that works, I don't have a problem with that.
>
> I think it does, but I worry that I'm missing some oddity in
> yum/dnf/mock parsing of the single config file.  I tested
> with mock-1.4.8 on Fedora 26.  Moving the epel repo section
> after the sclo* repos I was still able to install epel
> packages.  I was worried that the includepkgs might not be
> properly limited to the sclo repos, but it seems like it is.
> It's easy enough to remove it if that proves incorrect with
> wider testing.
>
> >> Technically, can't this be supported in epel-6 as well?
> >> (Please pardon me if I have overlooked a decision to only
> >> support DTS in epel-7.)
> >>
> > I don't know of any reason it would not work in EL-6 either. The spec
> files
> > I found using devtool-set only set it to rhel 7.
>
> Yeah, I imagine we're at the point where most people
> building things which require a newer compiler are moving to
> EL-7.  I could have used it while trying to build znc-1.6
> for EL-6 a year or so ago.
>
> (I ended up building znc with clang instead.  I was going to
> send the patch to the znc maintainers in EPEL, but it got
> dropped in EL-6 before I had time to do so.)
>
>
I don't think it would be a problem, and may be useful for EL-6 as we still
have more EL-6 users than EL-7 users. That said, I am also not wanting to
break the world here. If people with more experience with the devtoolset
think it would make things harder in EL-6 or would need other flags to
work.. we can put them in the appropriate section.


-- 
Stephen J Smoogen.
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to