public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Meira <fmeira@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] how to control portage space usage
Date: Sun, 7 Aug 2005 20:22:10 +0000	[thread overview]
Message-ID: <a3c2e88b0508071322df976a8@mail.gmail.com> (raw)

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

Hi,
this is probably an old discussion, sorry for bring it up again.

When I joined Gentoo (a few months ago) I got the idea that I could control 
very well the space that gentoo would require. That would be great because 
of my 4.6G available to it. Then, not so long time ago I got very surprised 
with how much less space available I had when I didn't have (almost) 
anything installed. Now it's completely full and I'm the middle of an emerge 
:(

Well, tears apart, I would like to know if there's a good way to control the 
space usage of portage, since it is the reason for my problem. 
My /usr/portage and /var/tmp/portage/ take 2.2G which is almost half of the 
partition.

What I have installed:
- some (split) ebuilds of kde 3.4.1
- e16
- e17
- firefox
- gimp
- acrobat reader 7
- xmms, amsn (and maybe a few more small packages)

What I've found until now:
- clear /usr/portage/distfiles and /var/tmp/portage after an emerge, or 
regularly (using tmpreaper)
- there are some users-made scripts (still buggy) that look for old ebuilds 
in portage tree and erases them (
http://forums.gentoo.org/viewtopic-t-3011-highlight-portage+space+usage.html
)

Any comments/ideas/scripts about this, or everyone has plenty space to 
spare...

Cheers,
Fernando

[-- Attachment #2: Type: text/html, Size: 1698 bytes --]

             reply	other threads:[~2005-08-07 20:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 20:22 Fernando Meira [this message]
2005-08-07 20:50 ` [gentoo-user] how to control portage space usage Rumen Yotov
  -- strict thread matches above, loose matches on Subject: below --
2005-08-07 21:06 motub
2005-08-07 21:38 ` Fernando Meira
2005-08-07 22:04   ` Francisco J. A. Ares
2005-08-08  8:03     ` Neil Bothwick
2005-08-08  8:09       ` W.Kenworthy
2005-08-07 22:20   ` Tero Grundstr�m
2005-08-07 22:45     ` Fernando Meira
2005-08-08  7:45       ` Tero Grundstr�m
2005-08-08  9:30         ` Neil Bothwick
2005-08-08  9:44           ` Tero Grundstr�m
2005-08-08  9:53         ` Michael Kintzios
2005-08-08 10:20           ` Tero Grundstr�m
2005-08-08 13:00             ` Michael Kintzios
2005-08-08 13:13               ` Neil Bothwick
2005-08-08 18:23                 ` Fernando Meira
2005-08-08 19:10                   ` Neil Bothwick
2005-08-08 18:03         ` Fernando Meira
2005-08-08 10:48       ` Sean Reiser
2005-08-08 18:17         ` Fernando Meira
2005-08-08 18:54           ` Sean Reiser
2005-08-08 19:08             ` Luke Albers
2005-08-09 17:44             ` Fernando Meira
2005-08-09 18:25               ` Sean Reiser
2005-08-09 21:00                 ` Fernando Meira
2005-08-09 21:21                   ` Holly Bostick
2005-08-09 22:35                     ` Fernando Meira
2005-08-08 13:43   ` Richard Fish
2005-08-08 18:34     ` Fernando Meira

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=a3c2e88b0508071322df976a8@mail.gmail.com \
    --to=fmeira@gmail.com \
    --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