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] world favorites: pros and cons
Date: Wed, 5 Jul 2006 14:21:42 +0100	[thread overview]
Message-ID: <20060705142142.2ce7e2ef@hactar.digimed.co.uk> (raw)
In-Reply-To: <44ABB409.4080003@ilievnet.com>

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

On Wed, 05 Jul 2006 15:43:53 +0300, Daniel Iliev wrote:

> That is correct. What are the disadvantages besides the longer seeks for
> updates?

What longer seeks? --update only check one level of dependencies for
updates, a few seconds at most. That's nothing compared with the time you
could spend trying to fix a broken system.

> I have no problem with the redundant cruft - when I want just to try
> some package I do "emerge --pretend" and record the list of dependencies
> it wants to pull-in. If I decide the package is not useful to me, I
> "un-emerge" not only the package, but also the dependencies it had
> pulled-in during its installation.

What if you installed something else with overlapping dependencies
between merging and unmerging? You'll break it because you have removed
its dependencies.

The world file is part of how portage manages dependencies, pollute it
with packages that should not be there and portage will not work as it
should.


-- 
Neil Bothwick

Someone who thinks logically is a nice contrast to the real world.

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

  parent reply	other threads:[~2006-07-05 13:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  9:48 [gentoo-user] world favorites: pros and cons Daniel
2006-07-05 10:10 ` Neil Bothwick
2006-07-05 10:21   ` Alexander Skwar
2006-07-05 10:18 ` Alexander Skwar
2006-07-05 10:55   ` Neil Bothwick
2006-07-05 11:11     ` Daniel
2006-07-05 11:33       ` Rumen Yotov
2006-07-05 11:54         ` Daniel Iliev
2006-07-05 12:14       ` Neil Bothwick
2006-07-05 12:43         ` Daniel Iliev
2006-07-05 13:16           ` Alexander Skwar
2006-07-05 14:47             ` Alan McKinnon
2006-07-05 13:21           ` Neil Bothwick [this message]
2006-07-05 14:29           ` Daniel Iliev
2006-07-05 15:08             ` Neil Bothwick
2006-07-05 16:53               ` Daniel Iliev
2006-07-05 20:15                 ` Neil Bothwick
2006-07-05 16:38           ` Richard Fish
2006-07-05 17:10             ` Daniel Iliev
2006-07-05 18:15               ` Richard Fish
2006-07-05 18:59                 ` Daniel Iliev
2006-07-05 19:47                   ` Richard Fish
2006-07-05 16:54           ` Daniel da Veiga
2006-07-05 18:30             ` Daniel Iliev
2006-07-05 19:17               ` Daniel da Veiga
2006-07-05 20:01                 ` Daniel Iliev
2006-07-28 18:30                 ` Enrico Weigelt
2006-07-28 18:46                   ` [gentoo-user] " Jim Ramsay
2006-07-28 18:57                     ` Alexander Skwar
2006-07-28 19:10                       ` Enrico Weigelt
2006-07-28 19:30                         ` Jim Ramsay
2006-07-28 20:39                           ` Daniel da Veiga
2006-07-28 21:03                             ` Jim Ramsay
2006-07-28 21:03                               ` Jim Ramsay
2006-08-07 16:53                           ` Enrico Weigelt
2006-07-05 22:27 ` [gentoo-user] " Daniel Iliev
2006-07-05 22:43   ` Ryan Tandy

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=20060705142142.2ce7e2ef@hactar.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