public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Tue, 4 Dec 2012 21:15:20 -0800	[thread overview]
Message-ID: <CAN0CFw1rX3gAjvsUjVsn3e_085Bn8snFfrc_F83bi4c_L=PB1Q@mail.gmail.com> (raw)
In-Reply-To: <50BECEC7.6040103@gmail.com>

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

> > I think you're right about that.  Can I configure eclean to wait a
> > certain number of days since a package was removed before cleaning it?
> >  Even if I only run it once per week, it could remove a package that
> > was updated yesterday that I find out I need tomorrow.
> >
> > - Grant
>
>
> -t, --time-limit=<time>    don't delete files modified since <time>
> <time> is an amount of time: "1y" is "one year", "2w" is "two weeks", etc.
> Units are: y (years), m (months), w (weeks), d (days) and h (hours).

Thanks Dale.

> I found that in man eclean.

I'm sorry, I didn't consider a parameter like that for some reason.

Should it be alright to depclean every day?  As long as I use --time-limit
with 'eclean packages', I should be able to reinstall anything that
depclean removes even if it's pruned from Portage.

- Grant

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

  reply	other threads:[~2012-12-05  5:16 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 [this message]
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
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='CAN0CFw1rX3gAjvsUjVsn3e_085Bn8snFfrc_F83bi4c_L=PB1Q@mail.gmail.com' \
    --to=emailgrant@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