There are a lot of packages that are only ever used at build time, and should thous not be depended upon with RDEPEND (easiest one to remember: autotools, but not limited to). It would be nice if repoman checked for those and issued a notice if they are in RDEPEND. It shouldn't be an error because there are legit runtime dependencies for almost all of them, but at least the developer should be put on the lookout for a mistake. For a list of possible packages to look for, check bug #221421. FWIW I'm sure qaludis has this check because I did help with it a long time, adding a few packages to the list. I'm sure there are more packages though, which probably are used in sectors I don't work myself. Maybe we could put the list available on the CVS so that we can update them as new packages are added...
Created attachment 153139 [details, diff] implement a new RDEPEND.suspect check I've just hard-coded the list for now. When we decide to move it somewhere else, we can do the same for the list of valid RESTRICT values.
This is fixed in 2.1.5.
can i get you to change dev-util/jam to dev-util/ftjam? i'm removing jam from the tree soon.
(In reply to comment #3) > can i get you to change dev-util/jam to dev-util/ftjam? i'm removing jam from > the tree soon. Done, thanks.
Many packages use dev-python/setuptools at run-time, so I removed dev-python/setuptools from the hard-coded list in r14170.