From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] small tip how to really "emerge world"
Date: Tue, 16 Sep 2008 01:35:12 +1200 [thread overview]
Message-ID: <8cd1ed20809150635g212acc1axce33c9e75f2a51ee@mail.gmail.com> (raw)
In-Reply-To: <48CE4DBD.9070808@metaphysis.net>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Mon, Sep 15, 2008 at 11:57 PM, Andreas Prieß <ap@metaphysis.net> wrote:
>
> I think, if you have a look at the emerge option
> --with-bdeps < y | n >
> you should be able to get really, really all possible updates with emerge
> and without further gimmicks.
>
> If it returns "0 packages" to update, try also this
>> (it takes very long time to finish, requires app-portage/portage-utils)
>>
>> # for f in `qlist -IC`; do emerge -puDvNt $f | grep ebuild; done
>>
>
> There should not be any difference if you use the mentioned option to
> emerge.
Unless of course
1) a package is installed
2) that package has been upgraded
3) that package is absent from world
4) no packages exist in world which that package is a dependant of ( via
recursive propogation )
However, imo, such entries should either be injected into world, or removed
:)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'
[-- Attachment #2: Type: text/html, Size: 1590 bytes --]
next prev parent reply other threads:[~2008-09-15 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 7:51 [gentoo-server] small tip how to really "emerge world" Tomasz Lutelmowski
2008-09-15 11:57 ` Andreas Prieß
2008-09-15 12:37 ` Tomasz Lutelmowski
2008-09-15 13:35 ` Kent Fredric [this message]
2008-09-15 14:35 ` Marius Mauch
2008-09-15 15:01 ` Andrew Gaffney
2008-09-16 2:14 ` Bryce Porter
2008-09-16 8:02 ` Mark
2008-09-16 8:59 ` Kent Fredric
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=8cd1ed20809150635g212acc1axce33c9e75f2a51ee@mail.gmail.com \
--to=kentfredric@gmail.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