-
Notifications
You must be signed in to change notification settings - Fork 2
Bad offered packages version order #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is not really a bug. Pacback does its best to sort the output but there is no guarantee that it will be able to perfectly sort the output. The sort function is called here...
If you want to figure out how to fix |
So I have looked at ordering in that way but versions are embedded in the filename which makes them extremely difficult to trim effectively. Unfortunately, version naming conventions are pretty arbitrary and don't always follow guidelines. A search of a filesystem will return:
Which trims to:
From here I could try and convert each package name into a tuple or list to parse version but this has a lot of issues. For instance, look at these potential package versions it would need to parse:
I honestly can't begin to explain how much of a nightmare these formats are. The best I have been able to do so far is : I've moved all the relevant sorting into pacback itself so you can see the code here:
|
The rule in my mind is pretty simple actually (then please, by all means, don't spend too much time on this if it becomes crazy in practice.. btw your regex guessing wrongly spelt packages is amazing) Put aside the optionally leading Put even aside that hypens and colons are even disallowed by the spec in pkgver, so in theory you could even treat them like normal separators. |
Describe the Bug:
10 seems understood as lesser than 6
Output of Command
Example, this is fine:
Example, this is bad
Machine:
The text was updated successfully, but these errors were encountered: