I would also add to this request: portlint(1) should whine if USES (and similar knobs) values are not sorted.
manually assign (typo in title prevented auto-assignment)
Implemented in my CVS repo pending the release of the next version.
Implemented in 2.15.5.
This is useless if USES+= is used in the context of options.
I am reopening this bug.
Please revisit the implementation as of 2.15.5 and do not warn about unavoidable unsorted stuff. (I think you may have to parse Makefile lines whether they are sorted in themselves, rather than the final variable contents.)
Sample port: sysutils/busybox.
compiler:nestedfct gmake tar:bz2 perl5
Obviously the last two are not in order, but that's because the port does (this is with vim markup):
FWIW, I think think danfe@ only intended for the sort check to be performed per-line and not evaluate it's value at the end.
Fixed in 2.15.6.
A commit references this bug:
Date: Mon Oct 13 05:53:57 UTC 2014
New revision: 370756
Update to 2.15.6.
* Check to make sure each instance of USES is properly sorted.
No, 2.6.15 still doesn't check sortedness of USE_PYTHON, like in this:
> USES= python
> USE_PYTHON= distutils autoplist
> NO_ARCH= yes
The original bug only referred to "USES" which should be fixed. If there are macros in need of sorting, open new bugs.