Re: Use for filedeps/rpmdeps data?

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2011-10-07 at 21:21 +0000, Daniel Lazzari wrote:
> Hey everyone,
> 
> I noticed today that one of our recipes takes a very long time to get
> through the do_package task. The recipe has a couple of binaries and a
> whole lot of assets (thousands of audio files). It takes over 20
> minutes for the do_package task to complete on my local desktop. I
> finally tracked it down to the package_do_filedeps function which
> appears to be running an rpmdeps process for each file in each
> package. As far as I can tell, it just then dumps that data to text
> files in pkgdata and only seems concerned with the binaries. Can
> anyone shed some light on what this info is used for? Should it only
> be concerned with executables and libraries (there is currently no
> filter on it)? Do I even need that data if we are using ipkg instead
> of rpm?

This is why there is a line in package.bbclass which says:

		if pkg.endswith('-dbg') or pkg.endswith('-doc') or pkg.find('-locale-') != -1 or pkg.find('-localedata-') != -1 or pkg.find('-gconv-') != -1 or pkg.find('-charmap-') != -1 or pkg.startswith('kernel-module-'):
			continue

since those are packages we know we're not going to get useful
information from. It finds perl and python module dependencies so its
not just executable binaries/libraries unfortunately :/.

It would probably be useful to have a way of flagging other packages as
uninteresting though. The idea is the information is used by all the
package backends. At present it is used more by some than by others and
the ipk backend is limited in its use iirc. That will be changing over
time though.

Cheers,

Richard