public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] emerge -C eselect-python disaster
Date: Sun, 24 Jan 2010 21:22:56 -0500	[thread overview]
Message-ID: <4B5D0080.8030708@gentoo.org> (raw)
In-Reply-To: <4B5CDFB3.3010108@gmail.com>

On 01/24/2010 07:02 PM, Dale wrote:
> Is there something that I am missing here? For me, system should
> include the things needed for booting and for the package manager to
>  work.

It should include the programs directly involved in booting, and the
package manager.  I'm not sure that it should contain their dependencies
- since that information can be derived from the packages themselves.

> As I pointed out in another reply, portage won't let you unmerge
> itself but it will let you unmerge a package that will render portage
> useless.

Well, it shouldn't allow you to unmerge anything that will render
ANYTHING useless without some explicit instruction to do so.

The documentation does warn of this behavior:

--unmerge (-C)
WARNING: This action can remove important packages! Removes  all 
matching packages.  This does no checking of dependencies, so it
may remove packages necessary for the proper operation  of your
system.  Its arguments can be atoms or ebuilds. For a dependency
aware version of --unmerge, use --depclean or --prune.

If you use --depclean to remove your package then you're safe.

Note - the command line option names are not well-chosen here.  -C 
should really be --unmerge-without-checking-dependencies-unsafe or some 
other obnoxious option, and --depclean should be the easy to type parameter.




  parent reply	other threads:[~2010-01-25  4:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24  5:12 [gentoo-dev] emerge -C eselect-python disaster Benny Pedersen
2010-01-24  9:03 ` Ulrich Mueller
2010-01-24  9:40 ` Petteri Räty
2010-01-24 11:07 ` Petteri Räty
2010-01-24 13:02   ` Ben de Groot
2010-01-24 16:53     ` Petteri Räty
2010-01-24 18:20       ` Ben de Groot
2010-01-24 20:19         ` Petteri Räty
2010-01-25  0:02           ` Dale
2010-01-25  1:53             ` Jacob Godserv
2010-01-25  2:28               ` Dale
2010-01-25  9:26                 ` Petteri Räty
2010-01-25 11:02                   ` Dale
2010-01-25 11:30                     ` Petteri Räty
2010-01-25 11:32                       ` Petteri Räty
2010-01-25 16:06                         ` Dale
2010-01-25 17:04                           ` Petteri Räty
2010-01-26  1:26                           ` [gentoo-dev] " Duncan
2010-01-25 16:20                         ` [gentoo-dev] " Jacob Godserv
2010-01-25 17:02                           ` Petteri Räty
2010-01-25 17:07                             ` Dale
2010-01-25 18:01                               ` Petteri Räty
2010-01-25 16:21                     ` Patrick Nagel
2010-01-25  2:22             ` Richard Freeman [this message]
2010-01-25  5:03               ` Dale
2010-01-25  9:25             ` Petteri Räty
2010-01-24 23:06         ` Richard Freeman
2010-01-24 11:29 ` Arttu V.
2010-01-24 13:03   ` Dale
2010-01-24 21:15 ` Mike Frysinger
2010-01-25 11:10   ` Arfrever Frehtes Taifersar Arahesis

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=4B5D0080.8030708@gentoo.org \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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