public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:2.1.9 commit in: man/
Date: Mon, 14 Feb 2011 04:31:36 +0000 (UTC)	[thread overview]
Message-ID: <dabe09e7589b9e8903c7fb1fe129b7b6859cdf68.zmedico@gentoo> (raw)

commit:     dabe09e7589b9e8903c7fb1fe129b7b6859cdf68
Author:     Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 13 08:56:42 2011 +0000
Commit:     Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Mon Feb 14 04:27:21 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=dabe09e7

ebuild.1: update outdated BUILD_PREFIX docs

This will fix bug #354387.

---
 man/ebuild.1 |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/man/ebuild.1 b/man/ebuild.1
index 1795a8b..cb6ebc2 100644
--- a/man/ebuild.1
+++ b/man/ebuild.1
@@ -39,8 +39,8 @@ this particular ebuild file.  The temporary build directory normally
 contains the extracted source files as well as a possible
 "install image" (all the files that will be merged to the local
 filesystem or stored in a package).  The location of the build
-directory is set by the BUILD_PREFIX variable.  For information
-on what this variable is, run \fIemerge [\-v] info\fR, or to override
+directory is set by the PORTAGE_TMPDIR variable.  For information
+on what this variable is, run \fIemerge \-\-info\fR, or to override
 this variable, see \fBmake.conf\fR(5).
 
 Note: Portage cleans up almost everything after a package has been



             reply	other threads:[~2011-02-14  4:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  4:31 Zac Medico [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-26 18:40 [gentoo-commits] proj/portage:2.1.9 commit in: man/ Zac Medico
2011-02-22  3:14 Zac Medico
2011-02-08 20:48 Zac Medico
2011-02-08 20:48 Zac Medico
2011-02-08  0:54 Zac Medico

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=dabe09e7589b9e8903c7fb1fe129b7b6859cdf68.zmedico@gentoo \
    --to=zmedico@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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