On 1/18/12 7:10 PM, Mike Frysinger wrote: > On Wednesday 18 January 2012 12:32:08 Paweł Hajdan, Jr. wrote: >> Same here. How about adding some warning to portage (maybe just in the >> developer profile) when files in NEEDED are provided by packages not in >> RDEPEND? > > atm, we'll get a lot of false positives due to over-linking. the libtool + > .la files "issue" is a general example. another one off the top of my head: > a > package uses GTK+, so it runs `pkg-config --libs gtk+-2.0`, and links against > a > lot more stuff than GTK+, but it doesn't list those deps itself, so it'd fail. > > we could extend the logic to assume anything not found in the pkg's RDEPEND, > but was found in the full RDEPEND tree, is simply an implicit dep like that, > but this quickly dilutes the usefulness i think :(.
Oh, I meant the full RDEPEND tree in the above terminology. It's not perfect indeed, but should catch most serious errors. Also, we could make the "direct RDEPEND" problem a non-fatal warning.
signature.asc
Description: OpenPGP digital signature
