Dmitry Marakasov

Well, all I'm going to say is that this scheme will never be honored by Repology because it cannot be meaningfully compared neither to upstream, nor to other repositories, nor...

> Since versions produced by this versioning scheme are as easy to recognize as versions produced by other versioning schemes No, they are not. Unlike any other snapshot schemes I've...

While the other problems with it remain, yes, at least it would be possible to reliably tell that it's not an upstream version. It won't allow to tell it from...

> These versions are upstream versions followed by .0.distance.digest suffix where distance is a decimal number and digest consists of at least 4 hexadecimal digits, so they are clearly recognizable....

Update: more windows and macosx specific repositories have emerged, which suggests the following idea: turn shadow flag into namespace-like thing. - Each repository may have a namespace defined - Default...

> The projects appeared on rubygems or pypi first, were shadowed, then appeared in a linux repo but were never unshadowed afterward even if they are packaged elsewhere now. It...

Also chaotic aur, hyperbola, parabola

Likely depends on #722

#722 and #1129 would allow to get this done. The plan: - [x] Refactor repository configs in such a way that fetcher and parser arguments are specified separately in their...

Further development that this change would unlock, even with partial implementation: - More interesting freshness metrics #62 - Multiple categories support #76 - Better packagelinks/homepages handling #119, #195, #476, #722,...