public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yogesh Sharma <ysharma@catprosystems.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] prioritising security updates
Date: Wed, 21 Sep 2005 21:24:42 -0700	[thread overview]
Message-ID: <4332320A.7010601@catprosystems.com> (raw)
In-Reply-To: <433224DC.7020408@munat.com>

Hi,

1. emerge -p world is basic emerge, it checks only packages written to
world file.

2. emerge -puD world is better then emerge -p as it does deep scan.

--update (-u)
              Updates  packages  to  the best version available, which
may not
              always be the highest version number due to masking for 
testing
              and  development.   This  will  also  update direct
dependencies
              which may not be what you want.  In  general,  use  this 
option
              only in combination with the world or system target.

--deep (-D)
              When used in conjunction with --update, this flag forces 
emerge
              to  consider  the entire dependency tree of packages,
instead of
              checking only the immediate dependencies of the packages. 
As an
              example, this catches updates in libraries that are not
directly
              listed in the dependencies of a package."

3.  emerge -np `qpkg -I -nc`  is my version of  -uD which I checks for
all installed packed including those are missed by -uD.

Thanks
YS

Ben Munat wrote:

> Yogesh Sharma wrote:
>
>> Hi,
>>
>> I usually do :
>>
>> emerge -np `qpkg -I -nc`
>>
>> once verified I do:
>>
>> emerge -n `qpkg -I -nc`
>>
>> or  emerge individual package from -p output.
>
>
> This is pretty cool... thanks.
>
> One interesting thing though: currently on my home machine, doing:
>
> emerge -np `qpkg -I -nc`
>
> or
>
> emerge -p world
>
> or
>
> emerge -puD world
>
> brings up three different orders for the list of packages to emerge.
> The "-p world" has fewer packages, but the other two have the same
> number but in different orders. I suppose that might just mean that
> order's not really significant in this case.
>
> b



-- 
gentoo-server@gentoo.org mailing list



  reply	other threads:[~2005-09-22 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 22:05 [gentoo-server] prioritising security updates Christopher Schwerdt
2005-09-06 22:16 ` Jeremy Brake
2005-09-07  2:04 ` Ben Munat
2005-09-07  5:51   ` Sune Kloppenborg Jeppesen
2005-09-07 16:21     ` Ben Munat
2005-09-13 22:26       ` Jonas 'data' Fietz
2005-09-21 16:45         ` Yogesh Sharma
2005-09-22  3:28           ` Ben Munat
2005-09-22  4:24             ` Yogesh Sharma [this message]
2005-09-22 16:03               ` Ben Munat
  -- strict thread matches above, loose matches on Subject: below --
2005-09-06  0:09 [gentoo-server] Virtual ssh users Yogesh Sharma
2005-09-06  0:26 ` Ben Munat
2005-09-06  6:08   ` ysharma
2005-09-06 16:41     ` Ben Munat
2005-09-06 21:53       ` [gentoo-server] prioritising security updates Jeremy Brake
2005-09-06 22:14         ` Paul Kölle
2005-09-07  6:12         ` Michael Irey
2005-09-07  6:48           ` W.Kenworthy
2005-09-07 15:28             ` Matthias Bethke
2005-09-07 22:56               ` William Kenworthy
2005-09-08 12:19                 ` Matthias Bethke
2005-09-07 12:21         ` xyon
2005-09-08 14:39         ` A. Khattri

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=4332320A.7010601@catprosystems.com \
    --to=ysharma@catprosystems.com \
    --cc=gentoo-server@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