Keep old behaviour of comparision.
Change: old-comparision
Purpose: Keep old behaviour of comparision.
Reason: Since release tags like 0.beta1.1 etc. are very common in
Blueprint information
- Status:
- Started
- Approver:
- Jeff Johnson
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Review
- Series goal:
- Accepted for 5.4
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Jeff Johnson
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I guess that '_rpmnotalpha' in rpmdb/rpmevr.c should fix the what was the initial motivation behind this, but there's still the issue of %mkrel usage forcing this to still be required.
Once %mkrel has been phased out after distepoch/disttag has been fully adopted, I guess we can eventually ditch this.
%mkrel is largely phased out and Disttag/Distepoch are "fully adopted".
While there may be minor consequences to switching, there are
worse consequences supporting peculiar per-vendor collation sequences
from almost a decade ago that have served their purpose.
Headed for the bit bucket after review: re-apply the 1 line patch if you
really want/need this deviant behavior. I see more benefit to achieving
a collation sequence that is closer to ASCII strcmp behavior personally:
I could be convinced otherwise.
