Re: opkg-make-index cache failing

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

On Thu, 2012-03-29 at 09:58 +0200, Martin Jansa wrote:
> Today I did some more tests and started using simple bash script to
> reindex all Packages files just once (instead of rebuilding common arch
> many times with bitbake package-index).
> 
> OPKG_MAKE_INDEX=~/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index
> DEPLOY_IPK=~/shr-core/tmp-eglibc/deploy/ipk/
> for PACKAGE_FILE in `find ${DEPLOY_IPK} -name Packages`; do
>   PACKAGE_DIR=`dirname ${PACKAGE_FILE}`
>   touch ${PACKAGE_FILE}
>   echo "Regenerating ${PACKAGE_FILE}"
>   time flock ${PACKAGE_FILE}.flock -c "${OPKG_MAKE_INDEX} -r ${PACKAGE_FILE} -p ${PACKAGE_FILE} -l ${PACKAGE_FILE}.filelist -m ${PACKAGE_DIR}/"
> done
> 
> And on my machine it takes really long to finish
> real    26m40.108s
> user    23m6.673s
> sys     0m14.464s
> 
> So I'll look into opkg-make-index changes again and to make it easier I would like 
> to move all oe-core local patches:
> http://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/opkg-utils/opkg-utils
> to yocto git repo:
> http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/
> should I send pull-request for opkg-utils repo here or somewhere else? e.g. yocto ML?

I've been advising people to do that kind of thing on the Yocto mailing
list since there is already lots of patch traffic on OE-Core...

Cheers,

Richard