On Fri, 2017-09-01 at 16:04 +0300, Alexander Kanavin wrote: > On 08/31/2017 09:46 PM, Haris Okanovic wrote: > > > > Setting PACKAGE_ENABLE_FILELIST option generates Packages.filelist > > on > > `bitbake package-index`, which is index of files provided by each > > IPK package in the feed. It's useful for figuring out which package > > provides a particular file/program/library/etc. > > > > Disabled by default since generating a filelist involves reading > > the > > payload of every package in the feed, a time and IO intensive > > operation > > many users won't want to run. Those who do may flip this switch. > > > > Testing: > > * Built an opkg index with PACKAGE_ENABLE_FILELIST unset and > > verified > > no Packages.filelist are generated. > > * Built with PACKAGE_ENABLE_FILELIST="1" and verified each > > subfeed > > has Packages.filelist; took ~3min longer for 8,200 IPKs. > > > The only way to discover that this option exists is to read the code > for OpkgIndexer. And it's specific to opkg, which is not reflected in > the option name at all. > > Can you instead just place the index generation into a custom recipe > that depends on package-index recipe?
I'm going to disagree with that, I don't want a separate recipe for this and I'm not sure that makes sense. I'm ok with adding an option but we need to come up with a better namespace. How about OPKG_PACKAGE_INDEX_FILELIST_GEN? (says its package index and opkg specific) Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
