public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-portage-files.xml
Date: Wed, 21 Jan 2009 06:44:51 +0000	[thread overview]
Message-ID: <E1LPWpX-0001f5-BL@stork.gentoo.org> (raw)

nightmorph    09/01/21 06:44:51

  Modified:             hb-portage-files.xml
  Log:
  stable portage version no longer uses /etc/make.conf.example, see the -dev ML. the 2008.0 handbooks should still reference the old location, though, as there is no released stage tarball with the new location in /usr/share.

Revision  Changes    Path
1.20                 xml/htdocs/doc/en/handbook/hb-portage-files.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml?r1=1.19&r2=1.20

Index: hb-portage-files.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-portage-files.xml	17 Apr 2008 21:21:14 -0000	1.19
+++ hb-portage-files.xml	21 Jan 2009 06:44:51 -0000	1.20
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml,v 1.19 2008/04/17 21:21:14 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml,v 1.20 2009/01/21 06:44:51 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 files and data.
 </abstract>
 
-<version>1.12</version>
-<date>2008-04-17</date>
+<version>1.13</version>
+<date>2009-01-20</date>
 
 <section>
 <title>Portage Files</title>
@@ -40,11 +40,11 @@
 
 <p>
 If you're planning on changing a configuration variable, <e>don't</e> alter
-<path>/etc/make.globals</path> or <path>make.defaults</path>. 
-Instead use <path>/etc/make.conf</path> which has precedence over
-the previous files. You'll also find a <path>/etc/make.conf.example</path>. As 
-the name implies, this is merely an example file - Portage does not read in 
-this file.
+<path>/etc/make.globals</path> or <path>make.defaults</path>.  Instead use
+<path>/etc/make.conf</path> which has precedence over the previous files. You'll
+also find a <path>/usr/share/portage/config/make.conf.example</path>. As the
+name implies, this is merely an example file - Portage does not read in this
+file.
 </p>
 
 <p>






             reply	other threads:[~2009-01-21  6:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  6:44 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-17 11:07 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-portage-files.xml Sven Vermeulen (swift)

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=E1LPWpX-0001f5-BL@stork.gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@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