[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r14975: Added a notice about what to do when encountering missing so (incognito/trunk)
Author: anonym
Date: 2008-06-05 19:04:49 -0400 (Thu, 05 Jun 2008)
New Revision: 14975
Modified:
incognito/trunk/building.html
Log:
Added a notice about what to do when encountering missing sources due to outdated ebuilds + some minor refinements.
Modified: incognito/trunk/building.html
===================================================================
--- incognito/trunk/building.html 2008-06-05 22:57:59 UTC (rev 14974)
+++ incognito/trunk/building.html 2008-06-05 23:04:49 UTC (rev 14975)
@@ -9,20 +9,22 @@
</p>
<p>
-Requirements in order to build the CD are:
+Requirements in order to build Incognito are:
<ul>
-<li><a href="http://www.gentoo.org";>Gentoo Linux</a> system OR Gentoo Linux chroot environment</li>
+<li><a href="http://www.gentoo.org";>Gentoo Linux</a> system OR Gentoo Linux chroot environment.</li>
<li><a href="http://packages.gentoo.org/packages/?category=dev-util;name=catalyst";>>=catalyst-2.0.4</a></li>
<li>Good understanding of catalyst, portage, Gentoo and Linux systems in general</li>
-<li>The Incognito sources (get them from <a href="https://tor-svn.freehaven.net/svn/incognito/";>here</a>) should be placed in <code>/usr/src/incognito</code> (this is currently assumed by the build-scripts and spec-files, unfortunately).</li>
+<li>The Incognito sources of you choice (get a branch, tagged release or trunk from <a href="https://tor-svn.freehaven.net/svn/incognito/";>here</a>), placed in <code>/usr/src/incognito</code> (this is currently assumed by the build-scripts and spec-files, unfortunately).</li>
</ul>
</p>
-<p>Here are the instructions. Note that these are not meant as a step-to-step guide really, but more as a set of pointers. It's assumed that you know what you're doing. If you don't, you might very well fail at some point even if you follow the preceeding steps precisely.</p>
+<p>Here are the instructions. Note that the following probably will not work as a step-to-step guide really. It's more a set of pointers. It's assumed that you know what you're doing, especially in terms of how portage and catalyst works. If you don't, you might very well fail at some point even if you followed the preceeding steps to the letter.</p>
+<p>Unfortunaley, due to the dynamic and time dependent nature of portage some sources (at least in the old releases) might not be available at the URIs specified in the ebuilds if they're outdated. Therefore, if some ebuild fails stating that the sources could not be located, you'll have to locate them manually and put them in <code>/usr/portage/distfiles</code>. Unless you have configured wget to use Tor in the catalyst build environment the same applies for the package <code>trans-proxy-tor</code> as it's only available from a Tor hidden service.</p>
+
<ol>
-<li><p>First of all you will need a portage snapshot. This can be done either by using one of the snapshots used for building the official Incognito releases, or by generating your own one that might be more up to date. Usually, if you're using the trunk sources (i.e. the development version) you should generate your own snapshot. Note that generating your own snapshot most likely will require alot more modifications and ebuild hacking to get working. If you're trying to build any of the tagged versions (i.e. any past Incognito release) you might want to get the snapshot for that release (if it's available) since you then avoid the above mentioned trouble.</p>
+<li><p>First of all you'll need a portage snapshot. This can be done either by using one of the snapshots used for building the official Incognito releases, or by generating your own one that might be more up to date. Usually, if you're using the trunk sources (i.e. the development version) you should generate your own snapshot. Note that generating your own snapshot most likely will require alot more modifications and ebuild hacking to get working. If you're trying to build any of the tagged versions (i.e. any past Incognito release) you might want to get the snapshot for that release (if it's available) since you then avoid the above mentioned trouble.</p>
<p>Choose any <b>one</b> of the following alternatives:</p>
@@ -61,7 +63,7 @@
<p>Note that you might have to update the <code>source_subpath</code> field in <code>arch/x86/livecd-stage1.spec</code> so that it matches the stage3 you just downloaded.</p>
</li>
-<li><p>To build the stages yourself catalyst will need another stage3 (not to be confused with the one you're going to build) to do the compiling from. Download an official Gentoo <code>stage3-i686-*.tar.bz2</code> (the latest is recommended) and place it in <code>/var/tmp/catalyst/builds/default/</code>. You can find this tarball on any of <a href=http://www.gentoo.org/main/en/mirrors2.xml>the Gentoo mirrors</a> (choose one that's close to you). The file can usually be found under <code>releases/x86/current/stages/</code>.</p>
+<li><p>To build the stages yourself catalyst will need another stage3 (not to be confused with the one you're going to build) to do the compiling from. Download an official Gentoo <code>stage3-i686-*.tar.bz2</code> (the latest is recommended) and place it in <code>/var/tmp/catalyst/builds/default/</code>. You can find this tarball on any of <a href=http://www.gentoo.org/main/en/mirrors2.xml>the Gentoo mirrors</a> (choose one that's close to you). The file can usually be found under <code>releases/<your-arch>/current/stages/</code>, where <code><your-arch></code> refers to the architecture of your Gentoo install (in most cases <code>x86</code> will work).</p>
<p>Generate a stage3 seed stage (stage3 depends on stage1 and stage2, so these will have to be built as intermediate steps). After this step any caches in <code>/var/tmp/catalyst</code> related to stage1, stage2 or stage3 may be removed. Only the stage3 tarball needs to be kept.</p>
<pre>
@@ -97,7 +99,7 @@
</p>
<ol>
-<li>Add or update ebuilds in <code>portage.overlay</code> (which uses the same directory hierarchy as <code>/usr/portage</code>). Make sure the manifest files are up to date by running the following command for each new or updated ebuild:
+<li>Add or update ebuilds in <code>portage.overlay</code> (which uses the same directory hierarchy as <code>/usr/portage</code>) and edit the files in <code>portage.config</code> if necessary. Make sure the manifest files are up to date by running the following command for each new or updated ebuild:
<pre>
ebuild /path/to/ebuild manifest
</pre>