Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<div class="gmail_quote">On Tue, Sep 13, 2011 at 10:13 PM, Jeremy Olexa <span dir="ltr"><<a href="mailto:darkside@g.o">darkside@g.o</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 2011-09-13 15:55, Askar Bektassov wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
My question is straightforward, under what circumstances emerge world<br>
re-emerges packages even if installed and updated?<br>
</blockquote>
<br></div>
So, strictly speaking, emerge takes an atom and will install that. In this case, 'world' is the atom. 'emerge world' will REINSTALL every atom in your world file (.../var/lib/portage/world). The canonical way to UPDATE all packages is with the short options "-uDN", emerge -pvuDN world.</blockquote>
<div><br></div><div>Jeremy, </div><div class="gmail_quote"><br></div><div class="gmail_quote">What a swift response! You effectively addressed my question: is it possible that when I was using Gentoo/Linux few years ago (<2007), portage behaved the way you described even if the user was not appending the --update option?</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">I might be wrong, but my memory suggests that on several machines with Gentoo/Linux installed from stage 1 I ended up using emerge world without the -u option and it always did the right thing (updating packages to the best version).</div>
<div class="gmail_quote"><br></div>Thank you in advance,<br clear="all">Askar Bektassov<br>(Аскар Бектасов)<br></div>
|
|
