Generic Package Registry doesn't allow version names with only major/minor rev, letters, etc.
Problem to solve
Generic Package Registry doesn't allow version names with only major/minor rev, letters, etc. Although Issue 273034 will address some of the problems my organization is having with Generic Package Registry versioning, it still won't be sufficient for some use-cases:
- openssl: openssl packages are of the format
[0-9]*\.[0-9]*\.[0-9]*[a-z]*
-- for example, 1.1.1g. I believe this issue covers this particular use-case (trailing non-numeric character). - wpa_supplicant: wpa_supplicant packages are of the format
[0-9]*\.[0-9]*
-- for example, 2.9. I'm not certain if this use-case is covered by this issue so far (only two numeric version digits instead of three). - startpar: startpar packages are of the format
[0-9]*\.[0-9]*\.[a-z]*
-- for example, 0.59.orig (trailing word after dot) - ebtables: etables packages are of the format
v[0-9]*\.[0-9]*\.[0-9]*\-[0-9]*
-- for example, v2.0.10-4. This one is a bit wacky, since arguably the preceding "v" ought to be omitted, so this one is certainly debatable. However, Issue 273034 will at least allow this one if we remove the preceding "v"
Intended users
All users of the Generic Package Registry feature using some real-world packages that aren't SemVer compliant.
User experience goal
The user should be able to add real-world Generic packages to the Generic Package Registry whose versions are not SemVer compliant.
Permissions and Security
This seems to be in-line with current permissions and shouldn't change anything regarding them. However, "Security" features can improve substantially if both this issue and Issue 320979 are implemented, since all packages could be included in the registry (instead of just some of them) and all could be scanned.