Bug 847619

Summary:	go-module.elcass: EGO_SUM code example isn't displaying correctly
Product:	Gentoo Linux	Reporter:	Randall <ran.dall>
Component:	Eclasses	Assignee:	William Hubbs <williamh>
Status:	UNCONFIRMED ---
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Randall 2022-05-26 21:13:36 UTC

On the documentation page: https://devmanual.gentoo.org/eclass-reference/go-module.eclass/index.html

The code example to extract an EGO_SUM shows...

`cat go.sum | cut -d" " -f1,2 | awk '{print "	`

When the correct example is...

`cat go.sum | cut -d" " -f1,2 | awk '{print "\t\"" $0 "\""}'`

Reproducible: Always

Comment 1 Mike Gilbert gentoo-dev

2022-05-27 15:48:07 UTC

EGO_SUM is deprecated anyway.

Comment 2 Randall 2022-05-27 15:53:32 UTC

> EGO_SUM is deprecated anyway.

Agreed. However, it could be still useful for folks trying to update older ebuilds.

NTM the new Go dependency model requires either the submitting party or Gentoo (which has a limited amount of hosting space) to host the *-dep.tar.gz; which has been the ongoing problem.

Currently, I'm not updating packages that already use EGO_SUM due to this issue. 

(Even as a Pro member of GitHub, I only have 1GB of bandwidth to 'host' the packages. NTM mainly packages also require Git-LFS due to their size, which also has hard limits.)

Comment 3 William Hubbs gentoo-dev

2022-05-28 20:03:55 UTC

The problem with EGO_SUM is it creates ebuilds and manifests that are
thousands of lines long and SRC_URI is limited in size because it gets
exported to the environment.

Another option was proposed to the PMS team (see #833567). I strongly
prefer this option since it would make packaging things like nodejs
easier as well, but it was rejected

So, the only allowable path for handling go ebuilds is to remove
EGO_SUM and use the *-deps tarballs.

Comment 4 Randall 2022-05-28 20:36:44 UTC

Thank you, William, for your response and bringing #833567 to my attention. It was quite the read, with a lot of strong opinions. As a pragmatist, I agree with your perspective in Comment #16, but  Michał also makes some excellent points. Still, a shame the PMS team didn't op to considering the option further, as the Go deps situation is currently a real pain.


>So, the only allowable path for handling go ebuilds is to remove
>EGO_SUM and use the *-deps tarballs.

Fair enough. I'll switch out the EGO_SUMs with *deps tarballs when I encounter them from now on. However, I might have to get creative with my Portage Deps GitHub repo (or buy a data pack or something). For example, some CNI Plugins have *-deps tarball close to 1GB which GitHub doesn't like.