You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
include releases at given index-timestamp, but include more recent revisions until a second timestamp
pin individual packages to specific revision (via sha256, I think we don't want "count")
The 1st and 2nd points are mutulally exclusive, 3rd should be repeated.
Currently we have
hackage.haskell.org,2020-03-22T14:34:00Z
like syntax, i.e. RepoNamecommatimestamp.
In #6597 I made configuration with colon instead of comma, at least for now. Yet, we need a syntax which works for all of above modifications, is not too convoluted and easy to parse, and perfectly also expandable.
One option is to use spaces.
The text was updated successfully, but these errors were encountered:
with general rule unqual-component-name like token (: specifiers)?.
Token is required to start with alpha character.
Note that HEAD is such. ISO8601 date and posix timestamps start with digit
and @ so are different.
Examples:
hackage.haskell.org HEAD
hackage.haskell.org 2020-03-24T14:34:00Z
hackage.haskell.org @a23345679
hackage.haskell.org 2019-12-31T23:59:59Z revisions-until:2020-03-24T14:34:00Z
hackage.haskell.org HEAD revision:tree-diff-1.2.3:b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c
That would look like in cabal.project or cabal.project.freeze file like
The 1st and 2nd points are mutulally exclusive, 3rd should be repeated.
Currently we have
like syntax, i.e. RepoName comma timestamp.
In #6597 I made configuration with colon instead of comma, at least for now. Yet, we need a syntax which works for all of above modifications, is not too convoluted and easy to parse, and perfectly also expandable.
One option is to use spaces.
The text was updated successfully, but these errors were encountered: