In spirit of the recent discussion on -dev: http://archives.gentoo.org/gentoo-dev/msg_1c3b47875b87c9d0a2c93baf98698047.xml I think it's good idea to add repoman check which will check that both DEPEND and RDEPEND are set in ebuild. This will helps us not to forget and set both as our policy suggests.
RDEPEND is the only one that's set automatically, so shouldn't we only warn if there's no RDEPEND assignment? Also, I can imagine that some ebuilds have empty DEPEND and RDEPEND (like things that really only depend on libc). For such cases, should we allow a missing RDEPEND assignment if DEPEND is also missing?
(In reply to comment #1) > RDEPEND is the only one that's set automatically, so shouldn't we only warn if > there's no RDEPEND assignment? > > Also, I can imagine that some ebuilds have empty DEPEND and RDEPEND (like > things that really only depend on libc). For such cases, should we allow a > missing RDEPEND assignment if DEPEND is also missing? First, emtpy != missing. We only care about missing here. If a packages really has no deps, it should state both DEPEND="" and RDEPEND="". As for the check, for now I suggest to only hceck for implicit RDEPEND assignments (RDEPEND is unset, DEPEND is non-emtpy) so it doesn't trigger for packages that get their deps completely from eclasses. If necessary it can later be adjusted to also check for unset DEPEND.
Created attachment 178936 [details, diff] detect case where DEPEND is set and RDEPEND is unset Since it's only triggered when DEPEND is set, it avoids false positives in cases when all deps come from the eclass(es).
This is fixed in 2.1.6.7 and 2.2_rc23.
