Open f-f opened 7 months ago
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: https://github.com/purescript/spago/blob/b5a8ab980010ad08ed0c305d7ff06d337d1a0e89/src/Spago/Db.purs#L70-L80
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: https://github.com/purescript/spago/blob/b5a8ab980010ad08ed0c305d7ff06d337d1a0e89/src/Spago/Db.purs#L70-L80