public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Francisco J. A. Ares" <frares@terra.com.br>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how to control portage space usage
Date: Sun, 07 Aug 2005 19:04:32 -0300	[thread overview]
Message-ID: <42F68570.5070408@terra.com.br> (raw)
In-Reply-To: <a3c2e88b05080714385aca905f@mail.gmail.com>

Fernando Meira wrote:

> Ok, so running through that forum I decided to try out some of the
> scripts to clean stale distfiles.
> The first one (distcleaner-0.0.2) returned a lot of errors. The second
> (distmaint.py) was too weird. Finally, (distclean.sh) seemed to be ok,
> and freed 255 MB. I could then end my emerge (eclipse). After the
> emerge I end-up with 805Mb free.
>
> As you say Holly, this is far from enough if I want to compile
> something big and also maybe for smaller apps. Which means that I have
> a problem.
> In fact, I have a 38GB disk on my laptop. My mistake was that I
> assumed that gentoo was not so space-consuming. Now I'll have to make
> some modifications, redo my partitions. What I would like was to clean
> once per all my windoz partition (9GB)... but from time to time I need
> it.. unless I find a replacement to all the things I need from there.
>
> Anyway, thanks for the replies.
> If someone has a nice script to maintain distfiles under control let
> me know. ;)
>
> Cheers,
> Fernando.
>

Not a script, but I have some machines with /usr/portage NFS'd to a
server (I'm thinking about doing the same with /var/tmp/portage/ also,
but don't know how to lock it to avoid colisions).

If you have a desktop, you can do the same, and also use distcc to
accelerate the builds.

Francisco

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-07 22:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 21:06 [gentoo-user] how to control portage space usage motub
2005-08-07 21:38 ` Fernando Meira
2005-08-07 22:04   ` Francisco J. A. Ares [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2005-08-07 20:22 Fernando Meira
2005-08-07 20:50 ` Rumen Yotov

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=42F68570.5070408@terra.com.br \
    --to=frares@terra.com.br \
    --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