Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publish go-mod/vendor as release artifact #1722

Open
ctr49 opened this issue Feb 19, 2024 · 0 comments
Open

publish go-mod/vendor as release artifact #1722

ctr49 opened this issue Feb 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ctr49
Copy link

ctr49 commented Feb 19, 2024

As also requested for syft, in syft/#2622, it would be great, if the vendor-dir could be included in the released artifacts.

What would you like to be added: To have an available and consistent dependency package for distributions that want to distribute grype.

Why is this needed:
For source packages, some (many/all?) distributions require all artifacts to build the package (including their dependencies) to be present if not relying on distribution specific library/include dependencies (which would be rather unusual for a go package). These dependencies also need to be available for offline usage and may not be fetched at compile time through the language-specific module resolver (i.e. go mod download or npm i). Usually this results in someone creating a tarball of the deps as vendor dir. But this tarball could be much easier created and made available by the source package (here) rather than by each distribution package maintainer. Also, there would be higher consistency across distributions when made available from an authoritative party.

Additional context:
Example: Gentoo's grype package has a tarball of all dependencies at https://dev.gentoo.org/~williamh/dist/grype-0.73.0-deps.tar.xz which makes the whole package update process unnecessarily complicated.

@ctr49 ctr49 added the enhancement New feature or request label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant