From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/handbook: hb-introduction-new-devs.xml
Date: Mon, 26 Apr 2010 19:17:55 +0000 (UTC) [thread overview]
Message-ID: <20100426191755.85F8F2C04C@corvid.gentoo.org> (raw)
nightmorph 10/04/26 19:17:55
Modified: hb-introduction-new-devs.xml
Log:
unlink dead keychain project, replace links to maintained keychain guide, fix GuideXML
Revision Changes Path
1.15 xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml?r1=1.14&r2=1.15
Index: hb-introduction-new-devs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-introduction-new-devs.xml 19 Sep 2009 16:43:42 -0000 1.14
+++ hb-introduction-new-devs.xml 26 Apr 2010 19:17:54 -0000 1.15
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml,v 1.14 2009/09/19 16:43:42 beandog Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-new-devs.xml,v 1.15 2010/04/26 19:17:54 nightmorph Exp $ -->
<sections>
-<version>1.0.4</version>
-<date>2008-05-03</date>
+<version>1.1</version>
+<date>2010-04-26</date>
<section>
<title>Using CVS</title>
@@ -65,7 +65,7 @@
</p>
<pre caption="Checking out gentoo-x86">
-# cvs -d username@cvs.gentoo.org:/var/cvsroot co gentoo-x86
+$ <i>cvs -d username@cvs.gentoo.org:/var/cvsroot co gentoo-x86</i>
</pre>
<p>
@@ -76,8 +76,8 @@
</p>
<pre caption="Updating in gentoo-x86">
-# cd gentoo-x86
-# cvs update
+$ <i>cd gentoo-x86</i>
+$ <i>cvs update</i>
</pre>
<p>
@@ -87,7 +87,7 @@
</p>
<pre caption="Checking out portage">
-# svn co svn+ssh://username@cvs.gentoo.org/var/svnroot/portage
+$ <i>svn co svn+ssh://username@cvs.gentoo.org/var/svnroot/portage</i>
</pre>
</body>
@@ -131,27 +131,27 @@
<pre caption="Adding a package">
<comment>(Replace CVSROOT with the location of your checked-out CVS tree.)</comment>
-# cd $CVSROOT/app-misc
+$ <i>cd $CVSROOT/app-misc</i>
<comment>(Always update before working in part of the CVS tree!)</comment>
-# cvs update
-# mkdir foo
+$ <i>cvs update</i>
+$ <i>mkdir foo</i>
<comment>(Here, we add the package directory foo to the CVS repository.)</comment>
-# cvs add foo
-# cd foo
+$ <i>cvs add foo</i>
+$ <i>cd foo</i>
<comment>(It's better to keep in-progress ebuilds in an overlay outside of your CVS tree.)</comment>
-# cp /path/to/foo-1.0.ebuild ./
+$ <i>cp /path/to/foo-1.0.ebuild ./</i>
<comment>(Make sure PORTDIR_OVERLAY is set to the CVS directory when creating manifests.)</comment>
-# repoman manifest
-# ${EDITOR} metadata.xml
+$ <i>repoman manifest</i>
+$ <i>${EDITOR} metadata.xml</i>
<comment>You don't necessarily need a files directory any more</comment>
-# cvs add foo-1.0.ebuild metadata.xml files
+$ <i>cvs add foo-1.0.ebuild metadata.xml files</i>
<comment>[Don't forget to create a ChangeLog - see the man page for echangelog.]</comment>
-# echangelog "New ebuild for foo. Ebuild written by me. Fixes bug #XXXXXX."
+$ <i>echangelog "New ebuild for foo. Ebuild written by me. Fixes bug #XXXXXX."</i>
</pre>
<p>
-See the <uri link="?part=2&chap=4">Gentoo
-Metadata</uri> section for more information on metadata.xml.
+See the <uri link="?part=2&chap=4">Gentoo Metadata</uri> section for more
+information on <path>metadata.xml</path>.
</p>
<p>
@@ -160,9 +160,9 @@
</p>
<pre caption="Removing old versions">
-# cd CVSROOT/app-misc/foo
-# cvs update
-# cvs remove -f foo-1.0.ebuild
+$ <i>cd CVSROOT/app-misc/foo</i>
+$ <i>cvs update</i>
+$ <i>cvs remove -f foo-1.0.ebuild</i>
</pre>
<p>
@@ -176,19 +176,20 @@
<body>
<p>
-Always use <c>repoman commit</c> rather than <c>cvs commit</c>. Repoman is a quality assurance (QA)
-tool that performs basic checks and creates Manifests. If any part of repoman's output is unclear,
-please see <c>man repoman</c>. Additionally, you may tire of entering your key passphrase repeatedly;
-keychain (<uri>http://www.gentoo.org/proj/en/keychain.xml</uri>) can help you.
+Always use <c>repoman commit</c> rather than <c>cvs commit</c>. Repoman is a
+quality assurance (QA) tool that performs basic checks and creates Manifests. If
+any part of repoman's output is unclear, please see <c>man repoman</c>.
+Additionally, you may tire of entering your key passphrase repeatedly; keychain
+(<uri>http://www.gentoo.org/doc/en/keychain-guide.xml</uri>) can help you.
</p>
<pre caption="Using repoman">
<comment>[Make sure there are no root-owned files present prior to running repoman!]</comment>
<comment>("scan" scans the current directory for QA issues. "full" is more complete.)</comment>
-# repoman scan
+$ <i>repoman scan</i>
<comment>("commit" does a scan, then commits, while also updating the Manifest. Make sure you
add a verbose and useful CVS ChangeLog message...)</comment>
-# repoman commit
+$ <i>repoman commit</i>
</pre>
</body>
@@ -198,10 +199,11 @@
<body>
<p>
-If you have noticable high ping times to the cvs server, you might want to use the ssh master slave
-setup where you only connect to the other ssh server once and let it do the next commands over that
-connection. This way you save the handshake overhead which may speed up the whole checkout/commit
-by factor 3. Just add the code snipped given below to your config
+If you have noticable high ping times to the cvs server, you might want to use
+the ssh master slave setup where you only connect to the other ssh server once
+and let it do the next commands over that connection. This way you save the
+handshake overhead which may speed up the whole checkout/commit by factor 3.
+Just add the code snippet given below to your config.
</p>
<pre caption="~/.ssh/config">
@@ -211,12 +213,12 @@
</pre>
<p>
-After doing so, you can enable a backgrounded master connection by running
+After doing so, you can enable a backgrounded master connection by running:
</p>
<pre caption="Open Master connection in background">
<comment>You can look the meaning of the parameters up in the manpage of ssh</comment>
-$ ssh -M -N -f ${USER}@cvs.gentoo.org
+$ <i>ssh -M -N -f ${USER}@cvs.gentoo.org</i>
</pre>
</body>
@@ -250,8 +252,8 @@
<p>
Developers have access to webhosting, http://dev.gentoo.org/~$YOURNAME. Please
-see the <uri link="http://www.gentoo.org/proj/en/infrastructure/dev-webspace.xml">
-Webspace Configuration Guide</uri> for details.
+see the <uri link="/proj/en/infrastructure/dev-webspace.xml">Webspace
+Configuration Guide</uri> for details.
</p>
</body>
next reply other threads:[~2010-04-26 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 19:17 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-05 0:31 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/handbook: hb-introduction-new-devs.xml Markos Chandras (hwoarang)
2013-05-10 18:57 Markos Chandras (hwoarang)
2012-03-18 10:19 Markos Chandras (hwoarang)
2011-06-29 20:07 JosA MarAa Alonso (nimiux)
2009-09-19 16:43 Steve Dibb (beandog)
2008-05-03 10:22 Petteri Raty (betelgeuse)
2008-05-03 10:21 Petteri Raty (betelgeuse)
2008-03-02 22:48 Petteri Raty (betelgeuse)
2007-11-01 20:32 Christian Heim (phreak)
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=20100426191755.85F8F2C04C@corvid.gentoo.org \
--to=nightmorph@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