On 15/07/2022 23.34, William Hubbs wrote:
On Mon, Jun 27, 2022 at 01:43:19AM +0200, Zoltan Puskas wrote:
In summary, IMHO the EGO_SUM way of handling of go packages has more
benefits than drawbacks compared to the vendor tarballs.
EGO_SUM can cause portage to break; that is the primary reason support
is going away.
We attempted another solution that was refused, so the only option we
have currently is to build the dependency tarballs.
That reads as if you wrote it under the assumption that we can only
either use dependency tarballs or use EGO_SUM. At the same time, I have
not seen an argument why we can not simply do *both*.
EGO_SUM has numerous advantages over dependency tarballs, but can not be
used if the size of the EGO_SUM value crosses a threshold. So why not
mandate dependency tarballs if a point is crossed and otherwise allow
EGO_SUM? That way, we could have the best of both worlds.
- Flow
