Hello,
as golang got deprecated in favor of Go-toolset[1] with release of RHEL 7.6[2] and as there has been interested[3]. I have unretired and reintroduced the golang package back in to the EPEL7. For time being I will keep updates on the same cadence as for EPEL6, i.e. keeping one version of GC for the duration of its upstream support, i.e. skipping every other major(1.X) release.
Currently package is in the bodhi update[4] and also update for epel6 is there[5], karma and testing will be much appreciated for both.
Reintroduction of the golang back to EPEL7 opens question if we(I guess as Go-SIG and epel/fedora community) should pursue the same (S)RPM macros setup as we have in Fedora, so we can get the whole Fedora's Go stack there. Is it even technically possible?(changing the minimal buildroot in EPEL7?) What do you think about it? Anybody interested?
JC
[1] https://tinyurl.com/y9g2vpv9 [2] https://tinyurl.com/y74gemxs [3] https://pagure.io/GoSIG/go-sig/issue/19 [4] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ba8845b83b [5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e36943c593
On Tue, Nov 27, 2018 at 2:32 PM Jakub Cajka jcajka@redhat.com wrote:
Hello,
as golang got deprecated in favor of Go-toolset[1] with release of RHEL 7.6[2] and as there has been interested[3]. I have unretired and reintroduced the golang package back in to the EPEL7. For time being I will keep updates on the same cadence as for EPEL6, i.e. keeping one version of GC for the duration of its upstream support, i.e. skipping every other major(1.X) release.
Currently package is in the bodhi update[4] and also update for epel6 is there[5], karma and testing will be much appreciated for both.
This is good news! Thank you for working on this.
Reintroduction of the golang back to EPEL7 opens question if we(I guess as Go-SIG and epel/fedora community) should pursue the same (S)RPM macros setup as we have in Fedora, so we can get the whole Fedora's Go stack there. Is it even technically possible?(changing the minimal buildroot in EPEL7?) What do you think about it? Anybody interested?
Absolutely. I've received multiple requests to package syncthing for EPEL7, but haven't been able to do so because dependencies are either missing or hilariously outdated. So any attempt to improve the golang situation on EPEL7 further is welcome.
Fabio
JC
[1] https://tinyurl.com/y9g2vpv9 [2] https://tinyurl.com/y74gemxs [3] https://pagure.io/GoSIG/go-sig/issue/19 [4] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ba8845b83b [5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e36943c593 _______________________________________________ golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an email to golang-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
----- Original Message -----
From: "Fabio Valentini" decathorpe@gmail.com To: golang@lists.fedoraproject.org Sent: Tuesday, November 27, 2018 4:35:38 PM Subject: Re: Golang back in EPEL 7
On Tue, Nov 27, 2018 at 2:32 PM Jakub Cajka jcajka@redhat.com wrote:
Hello,
as golang got deprecated in favor of Go-toolset[1] with release of RHEL 7.6[2] and as there has been interested[3]. I have unretired and reintroduced the golang package back in to the EPEL7. For time being I will keep updates on the same cadence as for EPEL6, i.e. keeping one version of GC for the duration of its upstream support, i.e. skipping every other major(1.X) release.
Currently package is in the bodhi update[4] and also update for epel6 is there[5], karma and testing will be much appreciated for both.
This is good news! Thank you for working on this.
Reintroduction of the golang back to EPEL7 opens question if we(I guess as Go-SIG and epel/fedora community) should pursue the same (S)RPM macros setup as we have in Fedora, so we can get the whole Fedora's Go stack there. Is it even technically possible?(changing the minimal buildroot in EPEL7?) What do you think about it? Anybody interested?
Absolutely. I've received multiple requests to package syncthing for EPEL7, but haven't been able to do so because dependencies are either missing or hilariously outdated. So any attempt to improve the golang situation on EPEL7 further is welcome.
Fabio
IMO biggest issue with dependencies will be that anything that is in the RHEL(and is not deprecated), can't be added in to the EPEL, that would left only vendoring/bundling as and option in some cases and complicate the packaging. Clearly sub-optimal, but at least we could add some higher profile packages if maintainers would be willing to maintain them.
JC
JC
[1] https://tinyurl.com/y9g2vpv9 [2] https://tinyurl.com/y74gemxs [3] https://pagure.io/GoSIG/go-sig/issue/19 [4] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ba8845b83b [5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e36943c593 _______________________________________________ golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an email to golang-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an email to golang-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
golang@lists.fedoraproject.org