public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "José Fonseca" <j_r_fonseca@yahoo.co.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Script to clean old files from /usr/portage/distfiles
Date: Tue, 12 Nov 2002 01:13:10 +0000	[thread overview]
Message-ID: <20021112011310.GB27162@localhost.localdomain> (raw)
In-Reply-To: <200211120042.41107.joba123@arcor.de>

On Tue, Nov 12, 2002 at 12:42:41AM +0100, Johannes Ball? wrote:
> Am Monday 11 November 2002 21:38 schrieb José Fonseca:
> > I never do `rm -f /usr/portage/distfiles'. I find very useful having the
> > sources of the installed packages ihandy as it avoids downloading
> > everything over andagain when updating to new releases of the same
> > version, or when installing Gentoo on another system. But after some
> > time that directory gets too fat and is too boring to eliminate the
> > deprecated packages by hand so I've made a script to automate this. You
> > can see it attached.
> 
> Sounds good! I was missing this feature ...
> 
> >
> > I've started with a shell script, then python, then I've read qpkg.sh,
> > ebuild.sh, portage.py and many others in the search of the easiest way
> > to do this. In the end everything boiled down to 2 lines - the rest is
> > just sintatic sugar!
> >
> > I hope you enjoy it.
> >
> > José Fonseca
> 
> When I run your script, though, I get this:
> 
> sed: can't read /usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.19: 
> No such file or directory
[...]

These are packages which were installed from your '/usr/local/portage'
or were removed from portage.

> 
> Could this be my fault? Sometimes when I was messing with the files in 
> /usr/portage I wasn't sure whether an 'emerge rsync' would fix it all up 
> again ...
> 
> I also have some stuff in /usr/local/portage ...

It's not really your fault, but just a limitation of the script. Please
read my second post for more info about this.

I decided not to flush the error output to /dev/null so that one is
alerted that the sources specific to these package [ do not belong to
any other]will get deleted.

I could write a variation of the script without these shortcomings -
that actually read the installed ebuilds which is *much* slower. I
personally don't need it as I only have little stuff in
/usr/local/portage.

If there is enough interest I'll add a couple of operation modes to the
script: "dummy", and "safe"; to make a dry-run and/or a safe evaluation
of the installed packages repectively.

José Fonseca
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2002-11-12  1:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 20:38 [gentoo-dev] Script to clean old files from /usr/portage/distfiles José Fonseca
2002-11-11 23:42 ` Johannes Ballé
2002-11-12  1:13   ` José Fonseca [this message]
2002-11-12  2:01     ` Marko Mikulicic
     [not found]       ` <20021111212849.A23035@twobit.net>
2002-11-12 10:21         ` José Fonseca
2002-11-12 11:28           ` William Kenworthy
2002-11-12 12:28             ` José Fonseca
2002-11-12 15:37           ` Nils Ohlmeier
2002-11-12 17:56             ` José Fonseca
2002-11-12 23:12               ` Nils Ohlmeier
2002-11-12  0:29 ` Marko Mikulicic
2002-11-12  0:54   ` José Fonseca
2002-11-12  1:50     ` Marko Mikulicic
  -- strict thread matches above, loose matches on Subject: below --
2003-03-25 18:55 DJ Cozatt
2003-03-25 20:34 ` Chris Bainbridge
2003-03-27  4:53   ` DJ Cozatt

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=20021112011310.GB27162@localhost.localdomain \
    --to=j_r_fonseca@yahoo.co.uk \
    --cc=gentoo-dev@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