public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: stuart@gentoo.org
Subject: [gentoo-portage-dev] re: confcache
Date: Fri, 08 Oct 2004 13:08:29 -0700	[thread overview]
Message-ID: <1097265907.8869.27.camel@localhost.localdomain> (raw)

Well... that's weird, attempted to send this directly to dan, having it
bail due to
'failed: relaying not allowed: danarmak@gentoo.org'
I assume I'm being an idiot and screwing up the address (or local
configuration)...

Either way, you might want to take a look at my implementation of
confcache in 
http://dev.gentoo.org/~ferringb/ebuild-daemon/51-pre20-cvs/

You can use SANDBOX_DEBUG_LOG and SANDBOX_DEBUG instead of modifying the
sandbox- works just the same.  Also, variables changing _will_ cause
configure to bail if they've been cached (cflags fex), so you might want
to either filter those entries (they start with ac_cv_env_), or rewrite
them (I went for rewrite, works although I worry about other cache
entries relying on the vars not changing).
Aside from that, there is also the md5'ing of /proc/cpuinfo- most users,
not an issue, as magnade pointed out, this is a killer for users that
have procs that adjust their frequency (laptops fex) for power saving-
this changes the md5 of /proc/cpuinfo pretty much continually,
invalidating the cache continually.
~brian


--
gentoo-portage-dev@gentoo.org mailing list


             reply	other threads:[~2004-10-08 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 20:08 Brian Harring [this message]
2004-10-09  9:45 ` [gentoo-portage-dev] re: confcache Dan Armak
2004-10-09 12:35   ` Brian Harring
  -- strict thread matches above, loose matches on Subject: below --
2005-11-15  1:43 [gentoo-portage-dev] confcache Brian Harring
2005-11-15  2:40 ` [gentoo-portage-dev] confcache Thomas Kirchner

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=1097265907.8869.27.camel@localhost.localdomain \
    --to=ferringb@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=stuart@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox