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

golist --to-install should list glide.*, Godeps.json and other snapshot files #36

Open
ingvagabund opened this issue Mar 13, 2018 · 0 comments
Labels
enhancement New feature or request guidelines Needs to be mentioned in the Go guidelines help wanted Extra attention is needed

Comments

@ingvagabund
Copy link
Contributor

ingvagabund commented Mar 13, 2018

Currently, there is only a limited number of projects that provide a snapshot with all their dependencies (and commits). We should enforce in the guidelines that each devel subpackage must ship either available snapshot file or generate one if not provided by upstream (and ship it).

I have an experimental implementation of gofed approx-deps that approximate glide.lock file for a specific project and its commit. It generates the snapshot of all dependencies one would get if he/she run go get at the date corresponding to the commit. So far I was able to build archives from all defined packages based on the generated glide.lock and glide.yaml files.

It's essential to provide such a file since if the tooling can assume the snapshot file is available and corresponding project can be built from the enumerated dependencies, the tooling can run various advanced analysis such as API backward incompatibility detection.

This will require collaboration with all packagers (and maybe upstream) and testing. The expected benefit is automatical detection of incompatible API changes before a Go package is even updated and/or pushed into stable.

@ingvagabund ingvagabund added enhancement New feature or request help wanted Extra attention is needed guidelines Needs to be mentioned in the Go guidelines labels Mar 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request guidelines Needs to be mentioned in the Go guidelines help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant