From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Handbook missing portage unpacking
Date: Sat, 11 Oct 2014 14:25:55 -0700 [thread overview]
Message-ID: <5439A063.8090604@gmail.com> (raw)
In-Reply-To: <loom.20141011T223538-530@post.gmane.org>
On 10/11/2014 01:37 PM, James wrote:
> James <wireless <at> tampabay.rr.com> writes:
>
>
>> I was just following the handbook for an amd64 install; I have
>> not looked at the handbook in a while. I downloaded the stage3
>> tarball and the portage-latest tarball at the same time, like I always
>> have done. The handbook give instructions for untaring the stage3, in
>> section 5, but not the portage tarball, or did I miss something?
>
> Well I see the emerge --sync takes care of installing a new portage.
> It's been a while; but I remember downloading a portage tarball and
> uppacking it?
>
>
Yes, the last couple of times I did a fresh install portage took care of
installing it. I don't remember when this change actually happened though.
From memory (a very sketchy memory, I might add, so check before doing
it) the command was:
$ tar xvjf portage-latest.tar.bz2 -C /usr/portage
> oh well, we'll see.
>
> No need to reply....
>
Meh, I noticed this a while ago but didn't think to mention it. The docs
were already updated then.
Dan
next prev parent reply other threads:[~2014-10-11 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 20:13 [gentoo-user] Handbook missing portage unpacking James
2014-10-11 20:37 ` [gentoo-user] " James
2014-10-11 21:25 ` Daniel Frey [this message]
2014-10-12 7:32 ` [gentoo-user] " Stroller
2014-10-12 15:43 ` Kerin Millar
2014-10-12 16:41 ` Rich Freeman
2014-10-13 2:12 ` [gentoo-user] " James
2014-10-13 2:28 ` Rich Freeman
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=5439A063.8090604@gmail.com \
--to=djqfrey@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