public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "emerge portage"
Date: Fri, 18 Apr 2008 13:36:21 +0200	[thread overview]
Message-ID: <200804181336.21660.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <2430.10.11.200.125.1208516980.squirrel@mail.gigle.biz>

On Friday 18 April 2008, robert anstuther wrote:
> Hi, I am new to Gentoo so accept my apologies if this is a blatently
> stupid question. I want to install the latest version of a package on
> our site, on checking the various gentoo boxes I discovered that the
> versions of the package varied a lot. therefore I ran "emerge --sync"
> this worked fine but finished with the message that a new portage was
> available and that I should run the command in the above subject
> field, and then update ALL my config files, I am worried that I mess
> up my kernel by proceeding, I have checked the wiki and read through
> the emerge docs, but it is still not totally clear to me, Any help or
> suggested further reading very much appreciated.
>
>
> Thanks, Boba.

Hi Boba,

Your questions are all fully explained in the Gentoo Handbook:

http://www.gentoo.org/doc/en/handbook/index.xml



It is perfectly normal for portage to want to update itself first when 
doing a system update. Portage will update, then it re-runs the system 
update so that the new system is now in charge.


-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list



      parent reply	other threads:[~2008-04-18 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 11:09 [gentoo-user] "emerge portage" robert anstuther
2008-04-18 11:28 ` dirk.heinrichs.ext
2008-04-18 11:36 ` Alan McKinnon [this message]

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=200804181336.21660.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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