Skip to content

Conversation

@DeedleFake
Copy link
Collaborator

No description provided.

@DeedleFake DeedleFake self-assigned this Mar 9, 2023
@flathubbot
Copy link
Contributor

Started test build 27348

@flathubbot
Copy link
Contributor

Build 27348 failed

@DeedleFake
Copy link
Collaborator Author

This may not work so well. A proper vendor directory includes a modules.txt file that lists all of the vendored modules and their versions to make sure that they match the go.mod file. If I just generate that file, it won't work fully as a safeguard against changes. Plus the file is kind of complicated to generate manually from what I can tell.

Maybe a small web service to automatically generate vendor directories and serve them as tarballs would simplify things. You could just something like https://www.example.com/deedles.dev/[email protected] and it would just hand you the fully populated vendor directory or something. I'm not sure about making the manifest dependent on a web service that I write and maintain, though, as if it ever goes down the builds will stop working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants