Re: [libvirt] [jenkins-ci PATCH 1/2] Stop building Go projects on CentOS 7
On Sat, 2018-12-22 at 01:36 -0500, Neal Gompa wrote:
On Fri, Dec 21, 2018 at 4:15 AM Andrea Bolognani
<abologna(a)redhat.com> wrote:
> At some point during the life of CentOS 7, the Go compiler
> and related packages appear to has been moved from out of
> the base repositories and into EPEL.
>
> Since as a rule we only rely on first-party repositories
> to fulfill build requirements, this means we can no longer
> build Go projects on CentOS 7.
Software Collections don't count as first-party repositories? The RHEL
documentation recommends the Go Toolset in place of the deprecated
golang package. That said, the golang package isn't gone, it's just a
zombie now...
"First-party" might not the best word to describe it, but the
general idea is that we want to limit ourselves to packages that
are part of the operating system itself: this is mostly to maintain
sanity, because otherwise answering questions such as "what is the
newest version of Python available on $OS?" becomes quite tricky
due to the existence of EPEL, Software Collections, backports and
the like.
We currently have two exceptions to the above: we install Java from
backports on Debian 8, because otherwise we wouldn't be able to run
the Jenkins agent, and we install the nodebug kernel on Rawhide
because performance is quite awful with the regular one. Neither of
those exceptions affect whether we support a certain platforms, so
they're safe as far as I'm concerned.
--
Andrea Bolognani / Red Hat / Virtualization