public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Wed, 5 Dec 2012 12:50:12 +0000	[thread overview]
Message-ID: <20121205125012.29ea6228@digimed.co.uk> (raw)
In-Reply-To: <CAN0CFw2ACyQG7YkDgmumtwrdKvy4m6ELDQ7pvVd_BS0=RLz2nA@mail.gmail.com>

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

On Tue, 4 Dec 2012 20:04:30 -0800, Grant wrote:

> > The first depclean is redundant, you haven't updated anything so it
> > won't  
>> show anything useful. I only run depclean and revdep-rebuild weekly,I
>> don't see a need to routinely do it more often, especially on slower
>> systems. I do run eix-update and eix-update-remote after my daily
>> sync.I run eix-test-obsolete from the weekly cron script.
>> 
> I should have said that I'm emailed the results of the first set of
> commands so the first depclean is there to let me know what would be
> removed after yesterday's update.

But you ran depclean manually after yesterday's update, so it should show
nothing.


-- 
Neil Bothwick

CPU: (n.) acronym for Central Purging Unit. A device which discards or
distorts data sent to it, sometimes returning more data and sometimes
merely over-heating.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-12-05 12:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  0:30 [gentoo-user] System maintenance procedure? Grant
2012-12-05  1:00 ` nybblenybblebyte
2012-12-05  1:21 ` Dale
2012-12-05  3:55   ` Grant
2012-12-05  1:36 ` Neil Bothwick
2012-12-05  4:04   ` Grant
2012-12-05  4:34     ` Dale
2012-12-05  5:15       ` Grant
2012-12-05 10:22         ` Dale
2012-12-08  0:57           ` Grant
2012-12-08 22:04       ` Grant
2012-12-08 23:25         ` Dale
2012-12-15  3:38         ` Grant
2012-12-05 12:50     ` Neil Bothwick [this message]
2012-12-08  0:55       ` Grant
2012-12-05  3:15 ` Pandu Poluan
2012-12-05  3:29   ` Allan Gottlieb
2012-12-05  3:34   ` Dale
2012-12-05 10:05 ` Alan McKinnon
2012-12-08  0:56   ` Grant
2012-12-08 11:58     ` Neil Bothwick
2012-12-08 20:06     ` Alan McKinnon
2012-12-08 21:07       ` Grant
2012-12-08 21:25         ` Alan McKinnon
2012-12-08 21:54           ` Grant
2012-12-08 22:08             ` Alan McKinnon
2012-12-09  0:41               ` Grant
2012-12-08 22:49             ` Neil Bothwick
2012-12-08 23:20               ` Dale
2012-12-09  4:22                 ` Dale
2012-12-09 13:18                 ` Bruce Hill
2012-12-09 16:48                   ` Neil Bothwick
2012-12-09 17:01                     ` Bruce Hill
2012-12-09 19:06                       ` Neil Bothwick
2012-12-11 13:36                     ` Bruce Hill
2012-12-11 14:04                       ` Neil Bothwick
2012-12-11 17:20                       ` Michael Orlitzky
2012-12-12  6:05                       ` Alan McKinnon
2012-12-12  9:29                         ` Neil Bothwick
2012-12-12 15:10                         ` Bruce Hill
2012-12-12  9:49                       ` Neil Bothwick
2012-12-12 12:16                         ` design [depois das dez]
2012-12-09  0:33               ` Peter Humphrey
2012-12-10  7:50 ` Daniel Wagener
2012-12-10  8:41 ` [gentoo-user] " Steven J. Long

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=20121205125012.29ea6228@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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