Fedora 31 Self-Contained Change proposal: Adopt new Go Packaging Guidelines

<a href="" title=""></a>

== Summary ==

The [[PackagingDrafts/Go| current Go packaging guidelines]] have been in a draft
state for several years now, and they do not reflect the
[[ More_Go_packaging|current practices ]] from the Go SIG. As a result of new
RPM macros developed by [[User:nim| Nicolas Mailhot]], the Go SIG wishes to
formally adopt new Go Packaging Guidelines, which aim at automation, reliability
and simplicity.

== Owner ==
* Name: [[User:eclipseo| Robert-André Mauchin]]
* Name: [[User:jcajka| Jakub Cajka]]
* Name: [[User:nim| Nicolas Mailhot]]
* Name: [[User:qulogic| Elliott Sales de Andrade]]

* Email: < ... at lists dot>

== Detailed Description ==

Over 775 Go packages are currently residing in Fedora's repositories, yet no
formal guidelines have ever been approved. As a result, the various Go SPECs are
inconsistent and most often outdated. Moreover, the next version of Go, 1.13,
will introduce the concept of modules by default, which will completely change
how Go libraries are distributed. With the current state of our tooling, the Go
SIG is not prepared to face such a drastic change.

[[User:nim| Nicolas Mailhot]] has worked on a set of new RPM macros which
will allow us to disconnect the upstream Go tooling from the downstream
integration inside RPM. This will allow us to adapt easily to future upstream
changes without the need to rewrite our SPEC catalogue.

== Benefit to Fedora ==

* Simplicity: SPEC files are simpler, less error-prone
* Automation: the new macros computes packages definition, Requires,
Provides and has provision for the new automated BuildRequires
* Standardization of SPEC files across the Go library
* Drastic reduction of boilerplate and SPEC size
* Automatic removal of vendored code
* Ease of testing: all units tests are detected and run
* Ease of upkeep
* Ease of adaptation to upstream changes

== Scope ==

* Proposal owners:
** [
Get the last macros approved in ''redhat-rpm-config'']
** Get ''[ golist]'', the tool detecting
dependencies, updated and split from the
''[ go-compilers]''
** Release ''GOPATH'' directory ownership from the
''[ golang]'' package, so it
can be managed by the ''[
go-rpm-macros]'' package
** Get ''[ go-rpm-macros]'' packaged and reviewed
** Retire ''[
go-srpm-macros]'' and
''[ go-compilers]''
** Port existing Go packages to the new macros (it probably won't be
finished by [[Releases/31 | Fedora 31]])

* Other developers: N/A (not a System Wide Change)

* Policies and guidelines:
[ Get the Go
packaging guidelines approved by the Packaging Committee]

== Upgrade/compatibility impact ==

No compatibility impact is expected. All the new macros are backward compatible
with the old ones.

== How To Test ==

The COPR [ nim/macros-ng]
can be used to test the new macros on Rawhide. Sample SPEC files are available
in the FPC Guidelines proposal.

== User Experience ==

The user impact is minimal or nil. As a result of the simplification of SPEC
files, we may ship updated libraries more quickly, and it may be easier for new
contributors to package Go applications.

== Dependencies ==
N/A (not a System Wide Change)

== Contingency Plan ==

* Contingency mechanism: If the required packages are not merged by
the deadline target, or if the Guidelines are not approved, we may
continue with our current set of non-approved practices. No other
impact is expected.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
* Blocks product? No

== Documentation ==

The FPC Guidelines proposal is available on
eclipseo personal space].


Re: Fedora 31 Self-Contained Change proposal: Adopt new Go Packa

By Jakub Cajka at 04/15/2019 - 03:05

Hello, as much as this change proposal excites me and I'm looking forward to it. I'm unfortunately currently not able to own this change, regardless as much I would really like to.

I would also like to note that I have been added as owner arbitrarily, without notice and without my consent and therefore I would like to be removed from the owner list.


I believe this affects all packagers maintaining Go based packages as they should update their packages up to the new standard, so we don't fragment the package base. So IMO this should be system wide change.