public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] understanding --depclean
Date: Wed, 12 Nov 2008 11:13:00 -0600	[thread overview]
Message-ID: <491B0E9C.5050809@gmail.com> (raw)
In-Reply-To: <20081112090853.714c7933@digimed.co.uk>

Neil Bothwick wrote:
> On Tue, 11 Nov 2008 23:00:08 -0600, Dale wrote:
>
>   
>> Be very careful with --depclean.  It can really mess up something if you
>> are not watching close.
>>     
>
> That may have been the case some time ago, but depclean is much safer
> now. Notice that the warning at the start of its output has disappeared
> now?
>
>
>   

That is true but let's say a person updates python but forgets or
doesn't know,  to run python-updater, will --depclean know that?  What
if emerge doesn't work and they don't have buildpkg of some sort in
make.conf? 

I agree that --depclean is a LOT better but there are still situations
where it can mess up a system.   It is best to be careful and really
look at that list before letting it remove a package.  Basically, don't
type it in and walk off to let it do whatever it wants.

I also seem to remember that big warning when --depclean runs.  I think
that may still be there for a reason.  ;-) 

Dale

:-)  :-) 



  reply	other threads:[~2008-11-12 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  4:41 [gentoo-user] understanding --depclean Michael P. Soulier
2008-11-12  5:00 ` Dale
2008-11-12  9:08   ` Neil Bothwick
2008-11-12 17:13     ` Dale [this message]
2008-11-12 21:12       ` Neil Bothwick
2008-11-13 19:29         ` Dale
2008-11-12  9:19   ` KH
2008-11-12 17:15     ` Dale
2008-11-12  9:48 ` Vladimir Rusinov

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=491B0E9C.5050809@gmail.com \
    --to=rdalek1967@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