flora-server
flora-server copied to clipboard
Metadata revisions
How to best represent metadata revisions?
We should add a Maybe RevisionNumber
in the Release
record, with:
newtype RevisionNumber = RevisionNumber Word
I am growing increasingly convinced that we should not support metadata revisions. They are supposed to be transparent, and if we ever want to switch to a model closed to CAS, it's not great.
Idea: Being able to pin the revision number of a package. Unfortunately, Cabal cannot represent this at the moment, so this'll have to be merged on their side before it is actionable on our end
Very nice tool!
Currently the dependency ranges shown for a package are outdated as revisions are not taken into account (or there is a bug). This might make a package look outdated when in reality it is up-to-date.
Example: regex-base
On hackage: