Either:
A mass rebuild is safer but relies on the goodwill of every packager.
%prep
%(auto)setup
%forge(auto)setup
%autosetup
GOPATH setup is now done directly in %prep via %goprep instead of delaying it later with %gobuildroot.
%goprep
%gobuildroot
intermediary package build artifacts are now stored in %{gobuilddir}/src/ (for the GOPATH tree) and %{gobuilddir}/bin/ (for produced binaries)
%{gobuilddir}/src/
%{gobuilddir}/bin/
Replace the following
%prep %forgesetup / %forgeautosetup / %setup / %autosetup
with
%prep %goprep %patchX -pY # as many as necessary %gogenbr -r
(see also go-rpm-macros RFE 3
That requires fixing the specs that workaround %forgesetup breakage with various flags or %(auto)setup calls. %goprep has the same requirements as %forgesetup but does much more than just unpacking sources. It can not be substituted with %(auto)setup.
%forgesetup
%gobuildroot is still provided as a compat macro for now but very lightly tested and likely to break soonish.
%{gobuilddir}/bin
Change references to _bin/ to references to %{gobuilddir}/bin/
_bin/
%gochecks
%gocheck
Change %gochecks calls to %gocheck:
The new macro set permits more simplifications in existing spec files. However, those simplifications are not required to get existing specs to build. Therefore they are not listed here.
To get an idea of the new enhancements, take a look at the provided templates.
Metadata Update from @nim: - Issue unmarked as blocking: #20 - Issue marked as depending on: #23
Wait, when will this be in effect?
@eclipseo You need to read the full plan in #20 . @jcajka asked to break it into issues, but you can’t really understand their logic individually.
If anyone is doing automated changes, please use rpmdev-bumpspec to bump the Release number. No manual changelog editing like the last time.
Login to comment on this ticket.