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: Thu, 13 Nov 2008 13:29:22 -0600	[thread overview]
Message-ID: <491C8012.9000106@gmail.com> (raw)
In-Reply-To: <20081112211209.5cb0f8c4@zaphod.digimed.co.uk>

Neil Bothwick wrote:
> On Wed, 12 Nov 2008 11:13:00 -0600, Dale wrote:
>
>   
>>> 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?
>>     
>
> If packages depnd on the older version of python, depclean won't remove
> them. If it's just a matter of depending on the correct modules,
> python-updater will fix that after the older python has been removed.
>   

It seems portage has changed a lot in how it tracks things. 

>   
>> What if emerge doesn't work and they don't have buildpkg of some sort in
>> make.conf?
>>     
>
> Why would emerge stop itself working?
>   

From my unerstanding, if it can't find python, no worky.  See above tho.

>   
>> 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.
>>     
>
> While I always run it with --pretend first, that's because I'm more
> curious than paranoid. What are these situations in which it can really
> mess up a system and are they situations that any sensible user would put
> themselves in?
>
>   
>> I also seem to remember that big warning when --depclean runs.  I think
>> that may still be there for a reason.  ;-) 
>>     
>
> See above, that warning has been gone for some time. The preamble now
> contains this indication that depclean is a lot more cautious.
>
>  * As a safety measure, depclean will not remove any packages
>  * unless *all* required dependencies have been resolved.  As a
>  * consequence, it is often necessary to run `emerge --update
>  * --newuse --deep @system @world` prior to depclean.
>
>
>   

I haven't used it in a while so I was not aware that it was changed. 
Looks like there as been some new code added here as well. 

I still think it reasonable to say that a person should be careful. 
Nothing is perfect.  I know I watch it when I am doing some house cleaning.

Dale

:-)  :-) 





  reply	other threads:[~2008-11-13 19:29 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
2008-11-12 21:12       ` Neil Bothwick
2008-11-13 19:29         ` Dale [this message]
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=491C8012.9000106@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