As a part of a process of building all golang projects on various distributions (e.g. Fedora, RHEL, CentOS) from the same spec file I would like to propose ending support of all golang packages (or its parts) shipping source codes of projects written in Golang in RHEL7. All the packages are going to be replaced with their corresponding counterparts in epel7 branch (in a sense of update path).
The list of affected packages:
golang-github-coreos-go-systemd
golang-github-cpuguy83-go-md2man
golang-github-docopt-docoptgo
golang-github-fsouza-go-dockerclient
golang-github-godbus-dbus
golang-github-gorilla-context
golang-github-gorilla-mux
golang-github-guelfey-godbus
golang-github-kraman-go-netfilter-queue
golang-github-kraman-libcontainer
golang-github-kr-pty
golang-github-openshift-go-json-rest
golang-github-openshift-go-systemd
golang-github-spf13-cobra
golang-github-spf13-pflag
golang-github-syndtr-gocapability
golang-googlecode-crypto
golang-googlecode-go-crypto
golang-googlecode-net
golang-googlecode-sqlite
golang-launchpad-gocheck
All the mentioned golang packages are used for building other tools in RHEL7 only.
All of them up to golang-github-cpuguy83-go-md2man do not ship any binary that can be installed by a customer.
As all the packages are already released and available in repos, they can not be obsoleted.
All tools currently built from the golang packages can still be built without any problems as the packages will continue to live in the repositories.
However, the golang packages no longer get updated. All tools are recommended to bundle all their dependencies from now on if built in RHEL7 (and in a need of newer version of their dependency).
At the same time, the packages can not be renamed in epel7 as the virtual provides (e.g. golang(golang.org/x/net) needs to be identical.
Expected state after the change:
* no golang package/rpm supported in rhel that ships source code
* golang projects already packaged in RHEL or to be package in RHEL are built from bundled dependencies
* any source code of a golang project for RHEL7 is shipped in epel7 (as a new package or a package updating already existing go packages in RHEL7)
* all affected golang packages (or its parts) gets retired, all their already existing builds will not get affected and stay in brew
* for a case of golang-github-cpuguy83-go-md2man, the package gets either renamed to go-md2man or its devel subpackage gets removed
There is no hard/soft limit for the projects currently built from affected dependencies to bundle their dependencies right away.
As long as they are built from the same go dependencies, this change will not affect the building.
Comment 4Red Hat Bugzilla Rules Engine
2017-01-18 17:16:03 UTC
Product Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 14RHEL Program Management
2021-01-15 07:29:43 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.