All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: opkg-make-index cache failing
Date: Fri, 25 Nov 2011 16:53:38 +0000	[thread overview]
Message-ID: <1322240018.24330.37.camel@ted> (raw)
In-Reply-To: <27A3051A-BC1D-4937-B936-42760021F584@dominion.thruhere.net>

On Fri, 2011-11-25 at 16:38 +0100, Koen Kooi wrote:
> In OE-classic the opkg-make-index cache was working pretty well,
> do_rootfs only spent a few seconds doing opkg-make-index on
> incremental builds. In the OE-core world the situation is different,
> opkg-make-index will reindex every package on each do_rootfs run, so
> after a while building images starts taking *really* long, on my
> systemd (work/ on ssd, deploy on rotating media) it now takes
> ±7minutes just do refresh the opkg indices.
> 
> Since I can't blame sstate for this I suspect that pseudo gets in the
> way of the naive caching logic. Is there a simple way to turn off
> pseudo when running opkg-make-index?

You could try:

PSEUDO_DISABLED=1 opkg-make-index

or even

PSEUDO_UNLOAD=1 opkg-make-index

although the latter is a sledge hammer to crack a nut approach...

Cheers,

Richard




  reply	other threads:[~2011-11-25 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 15:38 opkg-make-index cache failing Koen Kooi
2011-11-25 16:53 ` Richard Purdie [this message]
2011-11-25 18:15   ` Koen Kooi
2011-11-25 19:59     ` Koen Kooi
2011-11-29 11:40       ` Martin Jansa
2012-03-29  7:58         ` Martin Jansa
2012-03-29  8:59           ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1322240018.24330.37.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.