nim reported a new issue against the project: `go-rpm-macros` that you are following:
`%goprep` should apply patches automatically, so there is no convenience gap with `%autosetup`.
This is generic work that should be done *redhat-rpm-config* side in forge macros and then reused in`%goprep`. Basically:
1. define a `patch_flags<suffix>` rpm variable holding the parameters that should be passed to `%patch<suffix>`
2. define a `default_flags<suffix>` fallback
3. define a `source_patches<suffix>` holding an ordered space separated list of patch suffixes associated with a particular forge/go source.
And then write the usual lua loops to apply it all at the right moment in the spec.
To reply, visit the link below or just reply to this email
I finished building the last package tonight and will be busy with life for the
upcoming months. So here's a TODO for the remaining stuff that needs work.
I've assigned go-sig to all the new packages in dist-git, added them to
Koschei and added most of them to Anitya.
Some package still need to be added manually:
Packages to add to Anitya manually
I added a PR to enable monitoring for all Go packages:
After the above packages have been added to Anitya, and the PR is merged, it
would be useful to ask Anitya to be "resync" to fill new bugs (there is a bug:
if you use the API to add packages, which I did, Anitya does not fill bugs if
needed). In order to do that, ask ~kindly~ Michal Konecny
<mkonecny(a)redhat.com> to refresh all Golang projects manually.
Some package still need to be unbootstrapped:
They need a lot of new dependencies to be packaged to make that work. It
wasn't possible for me to finish the unbootstrapping within a reasonable delay
and I won't have the time to pursue this.
go2rpm needs to be packaged. There might be a couple of bugs remaining but the
base functionality is there. If anyone feels up to the task, please package it
and assign the go-sig to it afterwards.
I hope this is not too much to ask. Please keep the SIG informed if you do one
of the task above.
I'm going over the Go executable packages and have found a few
duplicates. Package maintainers, please discuss the situation and pick
one to move forward with, so we don't have extra work to do between
Maintainers by package:
Packages by maintainer:
eclipseo golang-github-jamesclonk-vultr golang-github-joho-godotenv
I'm going through the remaining executables to update to the latest Go
macros, and I see that the dep package contains Obsoletes:godep.
Firstly, there's no version, which is against recommendations.
Secondly, godep is not retired. So what's going on here?
Is this really necessary?
$ ls -lh /usr/lib/golang/pkg/bootstrap/bin/
-rwxr-xr-x. 1 root root 4.4M May 9 09:28 asm
-rwxr-xr-x. 1 root root 4.7M May 9 09:28 cgo
-rwxr-xr-x. 1 root root 16M May 9 09:28 compile
-rwxr-xr-x. 1 root root 5.7M May 9 09:28 link
These compilers shouldn't be needed after the build, right?
So they shouldn't be installed and shipped in the RPM (and neither
the corresponding .a files).