As discussed in [1], the idea is to make repoman complain when the USE constraints in a dependency string can't be satisfied with the newest version that would match the dependency without USE constraints. In other words, if we have: foo-1 with USE=bar foo-2 without USE=bar bar-1 depending on foo[bar(-)] Repoman should complain (when scanning bar-1) that 'foo[bar(-)]' dependency can't be satisfied by foo-2, and will force the package to be locked at foo-1. Right now, Portage only silently locks the dependency for users. As a result, the package is outdated for a long time and at some point all hell breaks loose. Having the warning in place, we will have the opportunity to find such issues earlier and solve them. The developers will be either required to fix/update the dependency string to work with foo-2, or to use explicit "<foo-2" dependency that is clear in the restrictions it is enforcing and easier to grep for. [1]:https://archives.gentoo.org/gentoo-dev/message/ed97f631d84b748bc3e426c5302b6261
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
