8 Dec
2015
8 Dec
'15
4:13 p.m.
If this is the intended way to specify a version range, I don't see any need to introduce a dedicated syntax. It just has to be ensured that when checking dependencies, all requirements for a package have to be satisfied by the same package. Then, the given scenario would be rejected because "pkg1" providing "dependency=5" meets "dependency<=4", but "dependency>=3" is only met by "pkg2" providing "dependency=2", which are not the same. Unfortunately, I lack proper knowledge of the libalpm code responsible for this to offhandedly implement a solution.