[SOLVED][NVM]Help adding vendor files to a go project

[logrusx]

Hi, I'd like to fork the original repo and add the vendor files so I don't need to deal with packaging and hosting them. Unfortunately I don't know enough about how go projects work. Can anybody land a hand? I believe once I do it I'll be able to do it on my own from then on.

UPDATE: I'm trying to automate the generation of vendor files with GitHub CI actions, but no luck yet.

UPDATE2: I've been a victim of some self-deception that made me look for such a solution to the wrong problem, disregard that thread.

Best Regards,
Georgi

[spica]

If some module can not be fetched from internet, I use a local copy and use a `replace` directive in go.mod

[logrusx]

Thanks, but I want to put that online for people to use. I have at least several tents of users and can't ask them to do that. For one release I used GitHub to host the vendor tarball, but they changed the scheme the URL is build and now it includes some weird random numbers which I can't predict in the ebuild. In the same time I don't want to go and update the URL for every new release. Of course that is an option too but I want to first try doing it properly. I'll also supervise upstream's actions and correct them if necessary as they are breaking my patches with stupid line swaps and such.

So far I've added vendor/modules.txt but go-module_live_vendor complains it's only allowed in live ebuilds.

Best Regards,
Georgi