We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now it's hard to explore the relationship between a package, its versions, and the various package sets - there are only a few facilities:
spago ls packages
spago registry package-sets
We should improve on that, and have ways to:
For each of the points above, I propose that:
spago registry package-sets $SET
spago registry info $PACKAGE
I'll note that we already have all this info in the Spago DB, and even have code in place to query it, and most likely just needs to be exposed:
spago/src/Spago/Db.purs
Lines 70 to 80 in b5a8ab9
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Right now it's hard to explore the relationship between a package, its versions, and the various package sets - there are only a few facilities:
spago ls packages
will list the packages present in the package set that the project usesspago registry package-sets
will list the package sets that have been published, together with the compiler that they are compatible withWe should improve on that, and have ways to:
For each of the points above, I propose that:
spago registry package-sets $SET
to show which packages are in the setspago registry info $PACKAGE
with a list of which package set each version is present in.I'll note that we already have all this info in the Spago DB, and even have code in place to query it, and most likely just needs to be exposed:
spago/src/Spago/Db.purs
Lines 70 to 80 in b5a8ab9
The text was updated successfully, but these errors were encountered: