From: "Zac Medico (zmedico)" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/portage/doc: testing.xml
Date: Wed, 24 Mar 2010 07:57:04 +0000 [thread overview]
Message-ID: <E1NuLSa-00024c-3U@stork.gentoo.org> (raw)
zmedico 10/03/24 07:57:04
Modified: testing.xml
Log:
Update for svn -> git migration.
Revision Changes Path
1.6 xml/htdocs/proj/en/portage/doc/testing.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml?r1=1.5&r2=1.6
Index: testing.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- testing.xml 18 Feb 2009 21:18:51 -0000 1.5
+++ testing.xml 24 Mar 2010 07:57:04 -0000 1.6
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml,v 1.5 2009/02/18 21:18:51 zmedico Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/testing.xml,v 1.6 2010/03/24 07:57:04 zmedico Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/proj/en/portage/doc/testing.xml">
@@ -24,46 +24,47 @@
<date>2007-06-14</date>
<chapter>
-<title>Access to Portage SVN repositories</title>
+<title>Access to Portage GIT repositories</title>
<section>
<body>
-<p>The Portage sourcecode is maintained within a SVN repository on the Gentoo SVN server.
-This server is only accessible for Gentoo developers, for anonymous access see <uri>http://anonsvn.gentoo.org/</uri>.
-If you are a dev: The main repository is located at <uri>svn+ssh://cvs.gentoo.org/var/svnroot/portage/main</uri>,
+<p>The Portage sourcecode is maintained within a GIT repository on the
+<uri link="http://git.overlays.gentoo.org/">git.overlays.gentoo.org</uri>.
+If you are a dev: The main repository is located at
+<uri>git+ssh://git@git.overlays.gentoo.org/proj/portage.git</uri>,
please note that it is subject to strict access controls, only people listed
in the developers section on the portage project page are able to commit to it.</p>
-<note>It is assumed you know how to work with Subversion.</note>
-<note>The repository can be viewed over <uri link="http://sources.gentoo.org/viewcvs.py/portage/main/">viewcvs</uri></note>
+<note>It is assumed you know how to work with GIT.</note>
+<note>The repository can be viewed over
+<uri link="http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=summary">GitWeb</uri>
+</note>
<p>
The repository currently contains the following branches (incomplete list):
</p>
<ul>
-<li>trunk: the current main development line</li>
-<li>branches/2.1-experimental: the former development line, now abandoned (don't use it unless you want to backport stuff)</li>
-<li>branches/prefix: experimental branch with support for prefix installs</li>
-<li>branches/2.0.54: old stable maintenance branch, nothing happens here anymore</li>
-<li>branches/2.1.2: old stable maintenance branch, nothing happens here anymore</li>
-<li>branches/2.1.6: current stable maintenance branch</li>
+<li>master: the current main development line</li>
+<li>prefix: experimental branch with support for prefix installs</li>
+<li>2.1.7: current stable maintenance branch</li>
</ul>
-<note>The old CVS repository still exists, but is not updated anymore or used in any other way.</note>
+<note>The old SVN repository still exists, but is not updated anymore or used in any other way.</note>
</body>
</section>
</chapter>
<chapter>
-<title>Creating snapshots from Portage SVN repositories</title>
+<title>Creating snapshots from Portage GIT repositories</title>
<section>
<body>
-<pre caption="creating a snapshot from portage trunk">
-svn co svn://anonsvn.gentoo.org/portage/main/trunk
+<pre caption="creating a snapshot from portage master branch">
+git clone git://git.overlays.gentoo.org/proj/portage.git
major_version=2.2
-prev_release=rc1
-latest_rev=$(svn info trunk | grep '^Last Changed Rev:' | grep -o '[0-9]*$')
+prev_release=rc67
+latest_rev=$(date -u +%Y%m%d%H%M%S)
snapshot_version=${major_version}_${prev_release}_p${latest_rev}
-trunk/mkrelease.sh --anon ${snapshot_version}
+cd portage
+./mkrelease.sh ${snapshot_version}
</pre>
</body>
</section>
@@ -77,21 +78,21 @@
<p>There are various reasons why you'd want to have multiple versions of portage
available at the same time without having to install them as system default.
Examples would be to check which versions are affected by a specific bug, to
-test new features before deploying a new version or have a svn checkout available
+test new features before deploying a new version or have a GIT checkout available
for testing while keeping a stable release for normal operation.</p>
<p>As of Portage-2.1.2 one can have and use an arbitrary number of Portage
installations parallel to each other by adjusting the two environment variables
<e>PATH</e> and <e>PYTHONPATH</e>. For example if you have a checkout of the
-trunk branch at <path>/checkouts/portage/trunk</path> you'd set them like this:</p>
-<pre caption="settings to use portage trunk">
-export PYTHONPATH="/checkouts/portage/trunk/pym:${PYTHONPATH}"
-export PATH="/checkouts/portage/trunk/bin:${PATH}"
+master branch at <path>/checkouts/portage</path> you'd set them like this:</p>
+<pre caption="settings to use portage master branch">
+export PYTHONPATH="/checkouts/portage/pym:${PYTHONPATH}"
+export PATH="/checkouts/portage/bin:${PATH}"
</pre>
<p>With those settings calling tools like <c>emerge</c>, <c>repoman</c> or
<c>ebuild</c> will pickup the correct locations to import libraries. External
tools like gentoolkit or porthole may or may not respect those settings though.
Setting <e>PATH</e> isn't even necessary if you always call the commands by their full
-name (e.g. <c>/checkouts/portage/trunk/bin/emerge</c> instead of <c>emerge</c>).</p>
+name (e.g. <c>/checkouts/portage/bin/emerge</c> instead of <c>emerge</c>).</p>
</body>
</section>
</chapter>
next reply other threads:[~2010-03-24 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 7:57 Zac Medico (zmedico) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-17 20:32 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/portage/doc: testing.xml Zac Medico (zmedico)
2012-09-17 19:33 Zac Medico (zmedico)
2010-03-25 3:53 Zac Medico (zmedico)
2010-03-25 1:47 Zac Medico (zmedico)
2009-02-18 21:18 Zac Medico (zmedico)
2008-07-16 23:15 Zac Medico (zmedico)
2008-07-16 22:21 Zac Medico (zmedico)
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=E1NuLSa-00024c-3U@stork.gentoo.org \
--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