From: Marko Mikulicic <marko@seul.org>
To: "José Fonseca" <j_r_fonseca@yahoo.co.uk>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Script to clean old files from /usr/portage/distfiles
Date: Tue, 12 Nov 2002 03:01:51 +0100 [thread overview]
Message-ID: <3DD0610F.1060902@seul.org> (raw)
In-Reply-To: 20021112011310.GB27162@localhost.localdomain
José Fonseca wrote:
> On Tue, Nov 12, 2002 at 12:42:41AM +0100, Johannes Ball? wrote:
>
>>Am Monday 11 November 2002 21:38 schrieb José Fonseca:
>>
>>
>>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.
I ran "emerge linux-headers"
emerge (1 of 1) sys-kernel/linux-headers-2.4.19
/var/db/pkg/sys-kernel/linux-headers-2.4.19 exists
/usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.19 does not exist
/var/db/pkg/sys-kernel/linux-headers-2.4.18 does not exist
/usr/portage/metadata/cache/sys-kernel/linux-headers-2.4.18 exists
it seems strange to me. the cache is not up to date.
Is there a way to force the ebuild of the cache ?
> 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.
I'd have enough interest :-) . I never do an emerge whatever without "-p"
first. even if this data is not lost forever I have the habit of
checking first.
Marko
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-11-12 2:02 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
2002-11-12 2:01 ` Marko Mikulicic [this message]
[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=3DD0610F.1060902@seul.org \
--to=marko@seul.org \
--cc=gentoo-dev@gentoo.org \
--cc=j_r_fonseca@yahoo.co.uk \
/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