public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2009-02-01  0:02 Markus Ullmann (jokey)
  0 siblings, 0 replies; 7+ messages in thread
From: Markus Ullmann (jokey) @ 2009-02-01  0:02 UTC (permalink / raw
  To: gentoo-commits

jokey       09/02/01 00:02:22

  Modified:             userguide.xml
  Log:
  Respect older layman versions when referencing paths

Revision  Changes    Path
1.6                  xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.5&r2=1.6

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- userguide.xml	30 Oct 2008 19:35:20 -0000	1.5
+++ userguide.xml	1 Feb 2009 00:02:22 -0000	1.6
@@ -71,8 +71,7 @@
 <title>Getting Started With Overlays</title>
 <section>
 <body>
-<p>Use Gunnar Wrobel's layman to easily install and update overlays over
-time.</p>
+<p>Use Gunnar Wrobel's layman to easily install and update overlays over time.</p>
 </body>
 </section>
 
@@ -82,7 +81,13 @@
 <p>To install layman, follow these steps:</p>
 <pre caption="Installing layman">
 <i>emerge layman</i>
-<i>echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
+</pre>
+<pre caption="Telling Portage about layman-fetched repositories">
+<comment>(for layman 1.1)</comment>
+<i># echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf</i>
+
+<comment>(for layman 1.2 and up)</comment>
+<i># echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
 </pre>
 <note>
 Layman will create "/usr/local/portage/layman/make.conf" once you add






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2010-04-15 17:36 Sebastian Pipping (sping)
  0 siblings, 0 replies; 7+ messages in thread
From: Sebastian Pipping (sping) @ 2010-04-15 17:36 UTC (permalink / raw
  To: gentoo-commits

sping       10/04/15 17:36:39

  Modified:             userguide.xml
  Log:
  Quick fix correcting that we actually do offer hosted overlays

Revision  Changes    Path
1.7                  xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.6&r2=1.7

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- userguide.xml	1 Feb 2009 00:02:22 -0000	1.6
+++ userguide.xml	15 Apr 2010 17:36:39 -0000	1.7
@@ -214,7 +214,8 @@
 <body>
 <p>Q: Do you host overlays for users?</p>
 <ul>
-<li>A: No, we do not. If you want an overlay of your own on (git.)overlays.gentoo.org, you must first become a Gentoo developer.</li>
+<!--<li>A: No, we do not. If you want an overlay of your own on (git.)overlays.gentoo.org, you must first become a Gentoo developer.</li>-->
+<li>A: Yes, we do. Please see <uri link="http://blog.hartwork.org/?p=843">this post</uri> for instructions to get hosted.</li>
 </ul>
 </body>
 </section>






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2010-06-13 20:04 Sebastian Pipping (sping)
  0 siblings, 0 replies; 7+ messages in thread
From: Sebastian Pipping (sping) @ 2010-06-13 20:04 UTC (permalink / raw
  To: gentoo-commits

sping       10/06/13 20:04:10

  Modified:             userguide.xml
  Log:
  Fix "source [..]/make.conf" Layman intergration for Layman 1.3.x, patch by Shawn Baker

Revision  Changes    Path
1.8                  xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.7&r2=1.8

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- userguide.xml	15 Apr 2010 17:36:39 -0000	1.7
+++ userguide.xml	13 Jun 2010 20:04:10 -0000	1.8
@@ -86,8 +86,11 @@
 <comment>(for layman 1.1)</comment>
 <i># echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf</i>
 
-<comment>(for layman 1.2 and up)</comment>
+<comment>(for layman 1.2)</comment>
 <i># echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
+
+<comment>(for layman 1.3)</comment>
+<i># echo "source /var/lib/layman/make.conf" >> /etc/make.conf</i>
 </pre>
 <note>
 Layman will create "/usr/local/portage/layman/make.conf" once you add






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2010-07-13 21:52 Joshua Saddler (nightmorph)
  0 siblings, 0 replies; 7+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-07-13 21:52 UTC (permalink / raw
  To: gentoo-commits

nightmorph    10/07/13 21:52:27

  Modified:             userguide.xml
  Log:
  significant guideXML fixes, grammar fixes, rewrites to be more helpful. discovered while updating the documentation in the main tree to recommend layman instead of gensync, primpted by bug 305047.

Revision  Changes    Path
1.9                  xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.8&r2=1.9

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- userguide.xml	13 Jun 2010 20:04:10 -0000	1.8
+++ userguide.xml	13 Jul 2010 21:52:27 -0000	1.9
@@ -1,68 +1,110 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.9 2010/07/13 21:52:27 nightmorph Exp $ -->
 
-<guide link="/proj/en/overlays/userguide.xml">
+<guide>
 <title>Gentoo Overlays: Users' Guide</title>
 
 <author title="Author">
-  <mail link="stuart">Stuart Herbert</mail>
+  <mail link="stuart"/>
 </author>
-
 <author title="Author">
-  <mail link="jokey">Markus Ullmann</mail>
+  <mail link="jokey"/>
+</author>
+<author title="Editor">
+  <mail link="nightmorph"/>
 </author>
 
-<abstract>This guide helps users understand how to use the Gentoo Overlays service</abstract>
+<abstract>
+This guide helps users understand how to use the Gentoo Overlays service.
+</abstract>
 
+<!-- The content of this document is licensed under the CC-BY-SA license -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.1</version>
-<date>2008-10-30</date>
+<version>1.2</version>
+<date>2010-07-13</date>
 
 <chapter>
 <title>Introduction</title>
 <section>
 <title>Audience</title>
 <body>
-<p>This document has been written for all users of Gentoo.  If you are a Gentoo
+
+<p>
+This document has been written for all users of Gentoo. If you are a Gentoo
 developer or Gentoo staff member, and you want to be able to manage your own
-overlay, please see the <uri link="/proj/en/overlays/devguide.xml">Developers' Guide</uri>.</p>
+overlay, please see the <uri link="/proj/en/overlays/devguide.xml">Developers'
+Guide</uri>.
+</p>
+
 </body>
 </section>
 
 <section>
 <title>What Are Overlays?</title>
 <body>
-<p>"Overlays" are package trees for Portage.  They contain additional ebuilds for Gentoo.  They are maintained by Gentoo developers and projects but distributed separately from the main Portage tree.</p>
+
+<p>
+"Overlays" are package trees for Portage. They contain additional ebuilds for
+Gentoo. They are maintained by Gentoo developers and projects but distributed
+separately from the main Portage tree.
+</p>
+
 </body>
 </section>
 
 <section>
 <title>Why Use Overlays?</title>
 <body>
-<p>People create overlays for all sorts of reasons.  Here are a few of the main
-ones:</p>
+
+<p>
+People create overlays for all sorts of reasons.  Here are a few of the main
+ones:
+</p>
+
 <ul>
-<li>If you modify an ebuild in /usr/portage, your change will be lost the next time you emerge --sync.  But, if you put your modified ebuild into an overlay, your change is safe from emerge --sync.</li>
-<li>Because overlays are not the main Gentoo Portage package tree, they're a great place to develop and test an ebuild without fear of breaking the main Gentoo Portage package tree.</li>
-<li>Not every ebuild belongs in the Gentoo Portage package tree.  An overlay is a great place to store an ebuild until it is ready to go into the Gentoo Portage package tree.</li>
+  <li>
+    If you modify an ebuild in <path>/usr/portage</path>, your change will be
+    lost the next time you <c>emerge --sync</c>. But, if you put your modified
+    ebuild into an overlay, your change is safe from <c>emerge --sync</c>.
+  </li>
+  <li>
+    Because overlays are not the main Gentoo Portage package tree, they're a
+    great place to develop and test an ebuild without fear of breaking the main
+    Gentoo Portage package tree.
+  </li>
+  <li>
+    Not every ebuild belongs in the Gentoo Portage package tree. An overlay is
+    a great place to store an ebuild until it is ready to go into the Gentoo
+    Portage package tree.
+  </li>
 </ul>
+
 </body>
 </section>
-
 <section>
 <title>What is the Gentoo Overlays Project?</title>
 <body>
-<p>Gentoo Overlays provide social workspaces to allow Gentoo projects,
-developers and users to collaborate together on tomorrow's Gentoo packages.
-We do this by hosting overlays for Gentoo projects and developers.</p>
+
+<p>
+Gentoo Overlays provide social workspaces to allow Gentoo projects, developers
+and users to collaborate together on tomorrow's Gentoo packages. We do this by
+hosting overlays for Gentoo projects, developers, and users.
+</p>
+
 </body>
 </section>
-
 <section>
 <title>Are All Official Overlays Hosted On overlays.gentoo.org?</title>
 <body>
-<p>No.  Gentoo developers are free to put their overlay wherever suits them best; they don't have to use overlays.gentoo.org if they don't want to.</p>
+
+<p>
+No. Gentoo developers are free to put their overlay wherever suits them best;
+they don't have to use overlays.gentoo.org if they don't want to.
+</p>
+
 </body>
 </section>
 </chapter>
@@ -71,142 +113,210 @@
 <title>Getting Started With Overlays</title>
 <section>
 <body>
-<p>Use Gunnar Wrobel's layman to easily install and update overlays over time.</p>
+
+<p>
+Use <c>layman</c> to easily install and update overlays over time.
+</p>
+
 </body>
 </section>
-
 <section>
 <title>Installing Layman</title>
 <body>
-<p>To install layman, follow these steps:</p>
+
+<p>
+To install <c>layman</c>, follow these steps:
+</p>
+
 <pre caption="Installing layman">
-<i>emerge layman</i>
+# <i>emerge layman</i>
 </pre>
+
 <pre caption="Telling Portage about layman-fetched repositories">
 <comment>(for layman 1.1)</comment>
-<i># echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf</i>
 
 <comment>(for layman 1.2)</comment>
-<i># echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
 
 <comment>(for layman 1.3)</comment>
-<i># echo "source /var/lib/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /var/lib/layman/make.conf" >> /etc/make.conf</i>
 </pre>
+
 <note>
-Layman will create "/usr/local/portage/layman/make.conf" once you add
-your first overlay. But if you do not plan to install an overlay
-immediately you should ensure that this file actually exists and
-contains the empty variable "PORTDIR_OVERLAY". Otherwise portage will
-complain. You can run "echo PORTDIR_OVERLAY=\"\" >
-/usr/portage/local/layman/make.conf" in order to have the file created
-correctly.
+Layman will create <path>/usr/local/portage/layman/make.conf</path> once you add
+your first overlay. But if you do not plan to install an overlay immediately you
+should ensure that this file actually exists and contains the empty variable
+<c>PORTDIR_OVERLAY</c>. Otherwise Portage will complain. You can run <c>echo
+PORTDIR_OVERLAY=\"\" > /usr/portage/local/layman/make.conf</c> in order to have
+the file created correctly.
 </note>
+
 </body>
 </section>
-
 <section>
 <title>Listing The Available Overlays</title>
 <body>
-<p>To see the list of overlays available, run:</p>
-<pre caption="Listing the available overlays">layman -L</pre>
+
+<p>
+To see the list of overlays available, run:
+</p>
+
+<pre caption="Listing the available overlays">
+# <i>layman -L</i>
+</pre>
+
 </body>
 </section>
-
 <section>
 <title>Installing An Overlay</title>
 <body>
-<p>To install an overlay on your computer, run:</p>
+
+<p>
+To install an overlay on your computer, run:
+</p>
+
 <pre caption="Adding an overlay">
-layman -a &lt;overlay-name&gt;
+# <i>layman -a &lt;overlay-name&gt;</i>
 </pre>
-<p>For example, to install <uri link="http://overlays.gentoo.org/proj/php">the PHP overlay</uri>, run:</p>
+
+<p>
+For example, to install <uri link="http://overlays.gentoo.org/proj/php">the PHP
+overlay</uri>, run:
+</p>
+
 <pre caption="Adding the PHP overlay">
-layman -a php
+# <i>layman -a php</i>
 </pre>
+
 </body>
 </section>
-
 <section>
 <title>Installing Packages From An Overlay</title>
 <body>
-<p>After installing an overlay, you can install packages from it by running:</p>
-<pre caption="Installing A Package From An Overlay">
-emerge -av &lt;category&gt;/&lt;package&gt;
-</pre>
-<p>Portage automatically searches your main Portage tree (in /usr/portage), and
-all of the overlays that you've installed, and picks the latest version of the
-package that it can find.</p>
 
-<p>If Portage isn't picking up the package from the overlay, that's normally
+<p>
+After installing an overlay, you can install packages from it by running:
+</p>
+
+<pre caption="Installing a package from an overlay">
+# <i>emerge -av &lt;category&gt;/&lt;package&gt;</i>
+</pre>
+
+<p>
+Portage automatically searches your main Portage tree (in
+<path>/usr/portage</path>) and all of the overlays that you've installed, and
+picks the latest version of the package that it can find.
+</p>
+
+<p>
+If Portage isn't picking up the package from the overlay, that's normally
 because the package is marked ~arch, where "arch" is the architecture of your
-computer (normally x86).</p>
+computer. You'll need to keyword the package as explained in the <uri
+link="/doc/en/handbook/">Portage Handbook</uri>.
+</p>
+
 </body>
 </section>
-
 <section>
 <title>Updating An Overlay</title>
 <body>
-<p>To keep your installed overlays up to date, run:</p>
-<pre caption="Updating All Installed Overlays">
-layman -S
+
+<p>
+To keep your installed overlays up to date, run:
+</p>
+
+<pre caption="Updating all installed overlays">
+# <i>layman -S</i>
 </pre>
-<p>Please don't run this more than once a day, or you'll put too much strain on
-Gentoo's infrastructure.</p>
+
+<impo>
+Please don't run this more than once a day, or you'll put too much strain on
+Gentoo's infrastructure.
+</impo>
+
 </body>
 </section>
 </chapter>
 
 <chapter>
 <title>How To Get More Involved</title>
-
 <section>
 <title>Introduction</title>
 <body>
-<p>All Gentoo developers were users of Gentoo before they became developers and still are users.  Our users aren't just the reason Gentoo exists today; they're our future volunteers too.</p>
 
-<p>If you start contributing to a project, we'll give you write access to the
+<p>
+All Gentoo developers were users of Gentoo before they became developers and
+still are users. Our users aren't just the reason Gentoo exists today; they're
+our future volunteers too.
+</p>
+
+<p>
+If you start contributing to a project, we'll give you write access to the
 project's overlay, and we'll provide mentors to help you contribute.
-Eventually, if we like what you do and the way you do it, we'll invite you to
-go the whole hog and become a full Gentoo developer.</p>
+Eventually, if we like what you do and the way you do it, we'll invite you to go
+the whole hog and become a full Gentoo developer.
+</p>
+
 </body>
 </section>
-
 <section>
 <title>How To Get Started</title>
 <body>
-<p>If you want to contribute to an overlay, the best approach is to build a good
+
+<p>
+If you want to contribute to an overlay, the best approach is to build a good
 working relationship with the Gentoo developers who are responsible for the
-overlay.  You can find out who is responsible for each overlay by going to
-<uri link="http://overlays.gentoo.org">overlays.gentoo.org's homepage</uri>, and clicking on the link for the overlay in question.</p>
+overlay. You can find out who is responsible for each overlay by going to <uri
+link="http://overlays.gentoo.org">overlays.gentoo.org's homepage</uri>, and
+clicking on the link for the overlay in question.
+</p>
+
+<p>
+Different developers prefer to be contacted in different ways. Some hang out on
+IRC, and may have their own channels for their projects. Examples of these
+include the PHP project (#gentoo-php), and the Webapps project (#gentoo-web).
+Others prefer to be contacted by email only. The only way you'll find out is to
+try and make contact, and take it from there. Commonly people in #gentoo-bugs on
+freenode IRC know where to find the people in question.
+</p>
 
-<p>Different developers preferred to be contacted in different ways.  Some hang
-out on IRC, and may have their own channels for their projects.  Examples of
-these include the PHP project (#gentoo-php), and the Webapps project
-(#gentoo-web).  Others prefer to be contacted by email only.  The only way
-you'll find out is to try and make contact, and take it from there. Commonly people in #gentoo-bugs on freenode IRC know where to find the people in question.</p>
 </body>
 </section>
-
 <section>
 <title>Working With Subversion</title>
 <body>
-<p>Subversion is one version control software we use to manage the contents of our overlays.  If you have never used Subversion before, the Subversion book is an excellent way to learn Subversion.  You can buy it in dead-tree format if you prefer or read it online for free.
+
+<p>
+<uri link="http://subversion.apache.org">Subversion</uri> is one version control
+software we use to manage the contents of our overlays. If you have never used
+Subversion before, the Subversion book is an excellent way to learn Subversion.
+You can buy it in dead-tree format if you prefer or read it online for free.
 </p>
+
 </body>
 </section>
-
 <section>
 <title>Working With Git</title>
 <body>
-<p>Git is another version control software we use to manage the contents of our overlays.  To get in touch with it, see the tutorial provided on the homepage.</p>
+
+<p>
+Git is another version control software we use to manage the contents of our
+overlays. To get in touch with it, see the tutorial provided on the <uri
+link="http://www.git-scm.com">homepage</uri>.
+</p>
+
 </body>
 </section>
-
 <section>
 <title>Further Information</title>
 <body>
-<p>The Gentoo project (or developer) you're working with should be able to
-provide you with any further help and assistance that you need.</p>
+
+<p>
+The Gentoo project (or developer) you're working with should be able to provide
+you with any further help and assistance that you need.
+</p>
+
 </body>
 </section>
 </chapter>
@@ -215,11 +325,17 @@
 <title>Frequently Asked Questions</title>
 <section>
 <body>
-<p>Q: Do you host overlays for users?</p>
-<ul>
-<!--<li>A: No, we do not. If you want an overlay of your own on (git.)overlays.gentoo.org, you must first become a Gentoo developer.</li>-->
-<li>A: Yes, we do. Please see <uri link="http://blog.hartwork.org/?p=843">this post</uri> for instructions to get hosted.</li>
-</ul>
+
+<p>
+<b>Q:</b> Do you host overlays for users?
+</p>
+
+<p>
+<b>A:</b> Yes, we do. Please see <uri
+link="http://blog.hartwork.org/?p=843">this post</uri> for instructions on how
+to host your overlay on Gentoo infrastructure.
+</p>
+
 </body>
 </section>
 </chapter>






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2010-11-10  0:36 Sebastian Pipping (sping)
  0 siblings, 0 replies; 7+ messages in thread
From: Sebastian Pipping (sping) @ 2010-11-10  0:36 UTC (permalink / raw
  To: gentoo-commits

sping       10/11/10 00:36:44

  Modified:             userguide.xml
  Log:
  Fix location of layman's make.conf in userguide docs. Reported by Agostino Sarubbo (bug #344759)

Revision  Changes    Path
1.10                 xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.10&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.10&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.9&r2=1.10

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- userguide.xml	13 Jul 2010 21:52:27 -0000	1.9
+++ userguide.xml	10 Nov 2010 00:36:44 -0000	1.10
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.9 2010/07/13 21:52:27 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.10 2010/11/10 00:36:44 sping Exp $ -->
 
 <guide>
 <title>Gentoo Overlays: Users' Guide</title>
@@ -139,16 +139,16 @@
 <comment>(for layman 1.2)</comment>
 # <i>echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
 
-<comment>(for layman 1.3)</comment>
+<comment>(for layman 1.3 and later)</comment>
 # <i>echo "source /var/lib/layman/make.conf" >> /etc/make.conf</i>
 </pre>
 
 <note>
-Layman will create <path>/usr/local/portage/layman/make.conf</path> once you add
+Layman will create <path>/var/lib/layman/make.conf</path> once you add
 your first overlay. But if you do not plan to install an overlay immediately you
 should ensure that this file actually exists and contains the empty variable
 <c>PORTDIR_OVERLAY</c>. Otherwise Portage will complain. You can run <c>echo
-PORTDIR_OVERLAY=\"\" > /usr/portage/local/layman/make.conf</c> in order to have
+PORTDIR_OVERLAY=\"\" > /var/lib/layman/make.conf</c> in order to have
 the file created correctly.
 </note>
 






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2011-07-25  1:17 Sebastian Pipping (sping)
  0 siblings, 0 replies; 7+ messages in thread
From: Sebastian Pipping (sping) @ 2011-07-25  1:17 UTC (permalink / raw
  To: gentoo-commits

sping       11/07/25 01:17:54

  Modified:             userguide.xml
  Log:
  Mention USE="git subversion" for layman (bug #228427), fix mis-use of term "portage", move version to integer

Revision  Changes    Path
1.11                 xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.10&r2=1.11

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- userguide.xml	10 Nov 2010 00:36:44 -0000	1.10
+++ userguide.xml	25 Jul 2011 01:17:54 -0000	1.11
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.10 2010/11/10 00:36:44 sping Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.11 2011/07/25 01:17:54 sping Exp $ -->
 
 <guide>
 <title>Gentoo Overlays: Users' Guide</title>
@@ -23,8 +23,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.2</version>
-<date>2010-07-13</date>
+<version>2</version>
+<date>2011-07-25</date>
 
 <chapter>
 <title>Introduction</title>
@@ -125,7 +125,8 @@
 <body>
 
 <p>
-To install <c>layman</c>, follow these steps:
+Before you install layman it is worth mentioning that you probably want <c>USE=&quot;git subversion&quot;</c> for it.
+After adjusting use flags, to install <c>layman</c> you run:
 </p>
 
 <pre caption="Installing layman">
@@ -204,7 +205,7 @@
 </pre>
 
 <p>
-Portage automatically searches your main Portage tree (in
+Portage automatically searches your Gentoo main tree (in
 <path>/usr/portage</path>) and all of the overlays that you've installed, and
 picks the latest version of the package that it can find.
 </p>
@@ -213,7 +214,7 @@
 If Portage isn't picking up the package from the overlay, that's normally
 because the package is marked ~arch, where "arch" is the architecture of your
 computer. You'll need to keyword the package as explained in the <uri
-link="/doc/en/handbook/">Portage Handbook</uri>.
+link="/doc/en/handbook/">Gentoo Handbook</uri>.
 </p>
 
 </body>






^ permalink raw reply	[flat|nested] 7+ messages in thread

* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml
@ 2013-04-06 11:04 Pavlos Ratis (dastergon)
  0 siblings, 0 replies; 7+ messages in thread
From: Pavlos Ratis (dastergon) @ 2013-04-06 11:04 UTC (permalink / raw
  To: gentoo-commits

dastergon    13/04/06 11:04:20

  Modified:             userguide.xml
  Log:
  fixed deprecated references to /etc/make.conf, wrt #445192

Revision  Changes    Path
1.12                 xml/htdocs/proj/en/overlays/userguide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/overlays/userguide.xml?r1=1.11&r2=1.12

Index: userguide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- userguide.xml	25 Jul 2011 01:17:54 -0000	1.11
+++ userguide.xml	6 Apr 2013 11:04:20 -0000	1.12
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.11 2011/07/25 01:17:54 sping Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/userguide.xml,v 1.12 2013/04/06 11:04:20 dastergon Exp $ -->
 
 <guide>
 <title>Gentoo Overlays: Users' Guide</title>
@@ -14,6 +14,9 @@
 <author title="Editor">
   <mail link="nightmorph"/>
 </author>
+<author title="Editor">
+  <mail link="dastergon"/>
+</author>
 
 <abstract>
 This guide helps users understand how to use the Gentoo Overlays service.
@@ -24,7 +27,7 @@
 <license/>
 
 <version>2</version>
-<date>2011-07-25</date>
+<date>2013-04-06</date>
 
 <chapter>
 <title>Introduction</title>
@@ -135,13 +138,13 @@
 
 <pre caption="Telling Portage about layman-fetched repositories">
 <comment>(for layman 1.1)</comment>
-# <i>echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /usr/portage/local/layman/make.conf" >> /etc/portage/make.conf</i>
 
 <comment>(for layman 1.2)</comment>
-# <i>echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /usr/local/portage/layman/make.conf" >> /etc/portage/make.conf</i>
 
 <comment>(for layman 1.3 and later)</comment>
-# <i>echo "source /var/lib/layman/make.conf" >> /etc/make.conf</i>
+# <i>echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf</i>
 </pre>
 
 <note>





^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2013-04-06 11:04 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-10  0:36 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/overlays: userguide.xml Sebastian Pipping (sping)
  -- strict thread matches above, loose matches on Subject: below --
2013-04-06 11:04 Pavlos Ratis (dastergon)
2011-07-25  1:17 Sebastian Pipping (sping)
2010-07-13 21:52 Joshua Saddler (nightmorph)
2010-06-13 20:04 Sebastian Pipping (sping)
2010-04-15 17:36 Sebastian Pipping (sping)
2009-02-01  0:02 Markus Ullmann (jokey)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox