From: Rumen Yotov <rumen_yotov@dir.bg>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pruning /usr/portage/distfiles/
Date: Thu, 21 Jul 2005 19:43:45 +0300 [thread overview]
Message-ID: <42DFD0C1.9010103@dir.bg> (raw)
In-Reply-To: <loom.20050721T180922-661@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
James wrote:
>Hello,
>
>/usr is the only partion I seem to have trouble filling up. After
>poking around I've decided to 'prune' /usr/portage/distfiles.
>
>Before automating this action, via crontab, I'm soliciting
>any other, slicker/cooler/better method to auto prune
>/usr/portage/distfiles.
>
>What I have done manually is:
>EMOVING LARGE FILES IN /usr/protage/distfiles:
>find ./ -size +100000 -exec ls -lag {} \; | less
><lists large files>
>find ./ -size +100000 -print -exec rm {} \;
><prints & removes large files>
>again:
>find ./ -size +50000 -exec ls -lag {} \; | less
>find ./ -size +50000 -print -exec rm {} \;
>again:
>find ./ -size +20000 -exec ls -lag {} \; | less
>find ./ -size +20000 -print -exec rm {} \;
>
>REMOVING OLD FILES IN /usr/protage/distfiles:
>find ./ -mtime +180 -exec ls -lag {} \; | less
>find ./ -mtime +180 -print -exec rm {} \;
>
>Running these commands manually caused the
>/usr/ dir to reduce from 88% full to 55% full.
>
>Looking at the proposed lists of files to be removed, gave
>me some confidence that it was OK to remove the files.
>Suggestions as to better logic that I could integrate
>into a script is welcome.
>
>Before hacking these commands into a script, I'd be interested
>in comments and ideas....(a better mouse trap?) better logic,
>like progressively running the commands unti the disk space
>threshold is below 60% full or something.
>
>
>James
>
>
>
Hi,
Going by memory here, but think it's correct ;)
Check about FEATURES="... distclean ..." in your /etc/make.conf, IMHO
this is a FEATURE which allows you to clean/erase the source files after
an emerge.
Or use /var to hold your portage-tree (make.conf&ln -s /usr/portage
/var/portage ;) (i'm using this setup).
HTH. Rumen
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3397 bytes --]
next prev parent reply other threads:[~2005-07-21 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 16:22 [gentoo-user] pruning /usr/portage/distfiles/ James
2005-07-21 16:31 ` David Morgan
2005-07-21 17:30 ` [gentoo-user] " James
2005-07-21 16:43 ` Rumen Yotov [this message]
2005-07-21 17:29 ` James
2005-07-21 17:33 ` [gentoo-user] " Zac Medico
2005-07-21 21:33 ` Andreas Prieß
2005-07-21 21:59 ` Octavio Ruiz (Ta^3)
2005-07-22 17:24 ` [gentoo-user] " James
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=42DFD0C1.9010103@dir.bg \
--to=rumen_yotov@dir.bg \
--cc=gentoo-user@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