public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Stellard <tstellar@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] ccache cache deleted during stage2 build
Date: Tue, 31 Mar 2009 12:31:25 +0800	[thread overview]
Message-ID: <d24863920903302131m663bb5b2v660d82a6f6b454f5@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

I am using the latest version of catalyst from git(commit
16745ae35961557a1205b5c86419d1aa496fcdf7).  I noticed that when the
stage2-preclean-chroot.sh script calls cleanup_stages() in
chroot_functions.sh, it deletes everything in $CHROOT_PATH/var/tmp,
but since $CHROOT_PATH/var/tmp/ccache is still bound to
/var/tmp/ccache my cache that lives outside of the chroot is cleared
as well. I have attached a patch that appears to fix the problem.  I
am not sure if there are any ill side-effects from this patch, but
since the "clean" action sequence also clears /var/tmp/*, is it really
necessary to do it in the stage2-preclean-chroot.sh script?

-Tom Stellard

[-- Attachment #2: catalyst.diff --]
[-- Type: text/plain, Size: 350 bytes --]

diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index f91f53c..fe20194 100644
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -210,7 +210,6 @@ cleanup_stages() {
 	esac
 
 	rm -f /var/log/emerge.log /var/log/portage/elog/*
-	rm -rf /var/tmp/*
 }
 
 update_env_settings(){

             reply	other threads:[~2009-03-31  4:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  4:31 Tom Stellard [this message]
2009-04-01  3:18 ` [gentoo-catalyst] ccache cache deleted during stage2 build Andrew Gaffney
2009-04-01  3:41   ` Tom Stellard

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=d24863920903302131m663bb5b2v660d82a6f6b454f5@mail.gmail.com \
    --to=tstellar@gmail.com \
    --cc=gentoo-catalyst@lists.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