On Wednesday 18 January 2012 12:32:08 Paweł Hajdan, Jr. wrote: > On 1/18/12 4:48 PM, Donnie Berkholz wrote: > > On 10:05 Wed 18 Jan , Mike Frysinger wrote: > >> On Wednesday 18 January 2012 09:23:00 Agostino Sarubbo wrote: > >>> 3) Check your rdepend, where is possible with scanelf[3] and if you > >>> declare it, please, as you said, exclude gcc/glibc and all package > >>> from @system > >> > >> portage generates a NEEDED file in the vdb > > > > Awesome, never seen that before! > > 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 :(. -mike
signature.asc
Description: This is a digitally signed message part.
