Support non-numeric version numbers
This would allow Pakku to be indexed.
JRaspass
What I don't get about Pakku is in what way is version "ava-1" newer than "papa"? Version.new("ava-1") > Version.new("pupa")' returns false since I suspect its just alphabetical with no number parts. So I don't know how to support weird versions like this. If Pakku was on zef would zef even allow such a version "number"?
lizmat
good question
hythm
for version 'ava-1', my reasoning is I want to have a version system similar to the one Raku uses 6.c, 6.d ... but instead of using the number first and alphabieical last, I want to use the alphabetical first and number last. new minor version would be (increment the number part) ava-2, ava-3 ..., new major version would be (increment the alphabetical part, chose a butterfly name starting with "b"), for example "brimstone-1", next major version (a butter fly name starting with "c", and so on.
for version pup I would like to get rid of it from the ecosystem if possible, since I was trying different approaches and making a lot of changes, I was not considering it a stable version.
pupa*
JRaspass
ah okay, if its expected to go alphabetically then i think that'll work, i just need to expand my version logic to handle non numeric sections