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 11:10:12 +0100	[thread overview]
Message-ID: <20060705111012.3937d453@hactar.digimed.co.uk> (raw)
In-Reply-To: <44AB8AEF.70104@ilievnet.com>

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

On Wed, 05 Jul 2006 12:48:31 +0300, Daniel wrote:

> I know the use of "emerge --oneshot <some-packages>" emerges packages
> without recording them in the world set. I also know that all the
> packages installed as dependencies don't get recorded in the world set
> either.
> 
> I see only one advantage in this - the next time I do "emerge --update
> world" the checking for available updates would be faster because the
> world file doesn't contain all the packages that are actually emerged.
> 
> BUT...What happens if there are "critical" updates for packages not
> listed in the world?

You won't see them, nor any updates to packages that are only dependencies
of package not in world. In short, you break your system.

The only time I use --oneshot for new installs is when trying a package
to see if I want it. If I do, I add it to world with --noreplace. If I
don't find it useful, my next emerge --depclean reminds me to remove it.


-- 
Neil Bothwick

Foolproof operation: No provision for adjustment.

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

  reply	other threads:[~2006-07-05 10:19 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 [this message]
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
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=20060705111012.3937d453@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