Wrap long lines, and remove eol-whitespace.
Translators please ignore this change.
This commit is contained in:
parent
17cc9c98a8
commit
eecc7b09b2
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14209
1 changed files with 38 additions and 36 deletions
|
@ -42,8 +42,8 @@
|
|||
</abstract>
|
||||
|
||||
</articleinfo>
|
||||
|
||||
<!-- Introduction
|
||||
|
||||
<!-- Introduction
|
||||
|
||||
<sect1 id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
@ -62,7 +62,7 @@
|
|||
is responsible for maintaining a consistent ports tree that can be used
|
||||
to create the binary packages that accompany a given FreeBSD
|
||||
release.</para>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>The Ports Cluster</title>
|
||||
|
||||
|
@ -79,7 +79,7 @@
|
|||
generate packages that might work on some systems and not on
|
||||
others depending on what software was previously
|
||||
installed.</para>
|
||||
|
||||
|
||||
<para>The <quote>Ports Cluster</quote> for the x86 architecture
|
||||
currently consists of a master node (Dual Pentium III 733MHz)
|
||||
and 8 slave nodes (Pentium III 800MHz) to do the actual
|
||||
|
@ -87,7 +87,7 @@
|
|||
build takes over 24 hours. These machines are co-located with
|
||||
the other FreeBSD Project equipment at Yahoo's corner of
|
||||
Exodus in Santa Clara, CA.</para>
|
||||
|
||||
|
||||
<para>The <quote>Ports Cluster</quote> for the Alpha
|
||||
architecture consists of 7 PWS 500A machines donated by Compaq
|
||||
and also co-located with Yahoo's facilities.</para>
|
||||
|
@ -123,10 +123,10 @@
|
|||
<listitem><para>This file contains the free space on each disc
|
||||
and whether packages, distfiles, or both are allowed on any
|
||||
given disc. The first column is the disc name. It must be
|
||||
of the form <literal>disc[0-9a-z]</literal>. Currently it is setup to allow
|
||||
for 10 discs (4 for the release set and 6 for the toolkit).
|
||||
There is an implied extra disc called <quote>scratch</quote> where all of
|
||||
the remaining distfiles/packages land if they do not fit
|
||||
of the form <literal>disc[0-9a-z]</literal>. Currently it is setup
|
||||
to allow for 10 discs (4 for the release set and 6 for the toolkit).
|
||||
There is an implied extra disc called <quote>scratch</quote> where
|
||||
all of the remaining distfiles/packages land if they do not fit
|
||||
elsewhere. The second column can be either a 1 or 0, where 1
|
||||
says that it is okay to place packages on this disc. The
|
||||
third column works the same way, but it controls
|
||||
|
@ -150,8 +150,8 @@
|
|||
<term><filename>checkdeps.pl</filename></term>
|
||||
|
||||
<listitem><para>Makes sure all packages dependencies are
|
||||
satisfied given an <filename>INDEX</filename> file and a directory of
|
||||
packages.</para></listitem>
|
||||
satisfied given an <filename>INDEX</filename> file and a directory
|
||||
of packages.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
|
@ -176,11 +176,11 @@
|
|||
<varlistentry>
|
||||
<term><filename>scrubindex.pl</filename></term>
|
||||
|
||||
<listitem><para>This script removes lines from an <filename>INDEX</filename> file
|
||||
for packages that are not present. It also removes the
|
||||
XFree86 dependencies. NOTE: you will need to tweak the value
|
||||
of the <varname>xdep</varname> variable to make sure the version number is
|
||||
correct.</para></listitem>
|
||||
<listitem><para>This script removes lines from an
|
||||
<filename>INDEX</filename> file for packages that are not present.
|
||||
It also removes the XFree86 dependencies. NOTE: you will need to
|
||||
tweak the value of the <varname>xdep</varname> variable to make sure
|
||||
the version number is correct.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
|
@ -201,21 +201,21 @@
|
|||
them want to contain packages, distfiles, both, or
|
||||
neither.</para></listitem>
|
||||
|
||||
<listitem><para>Make sure you remove the <varname>gen</varname> directory if
|
||||
there is an old one laying around. This directory contains
|
||||
working files that will only be valid for the current
|
||||
<listitem><para>Make sure you remove the <varname>gen</varname>
|
||||
directory if there is an old one laying around. This directory
|
||||
contains working files that will only be valid for the current
|
||||
split.</para></listitem>
|
||||
|
||||
<listitem><para>On your first pass through a split it is best to
|
||||
fake the copying of packages and distfiles. This will save
|
||||
both time and diskspace while you do a couple of trial runs to
|
||||
make sure things fit, etc. In the
|
||||
<filename>oneshot.pl</filename> set the <varname>fake</varname> variable
|
||||
to 1 and instead of actually copying the files it will
|
||||
&man.touch.1; them. Be sure you turn this off or set <varname>fake</varname> to
|
||||
0 before you give the resultant discs to the person that will
|
||||
be mastering the discs otherwise they will get a directory full
|
||||
of zero-sized files.</para></listitem>
|
||||
<filename>oneshot.pl</filename> set the <varname>fake</varname>
|
||||
variable to 1 and instead of actually copying the files it will
|
||||
&man.touch.1; them. Be sure you turn this off or set
|
||||
<varname>fake</varname> to 0 before you give the resultant discs to
|
||||
the person that will be mastering the discs otherwise they will get a
|
||||
directory full of zero-sized files.</para></listitem>
|
||||
|
||||
<listitem><para>Make sure you have a recent copy of the
|
||||
<filename>print-cdrom-packages.sh</filename> and that it is
|
||||
|
@ -276,8 +276,9 @@
|
|||
non-cdromable packages/distfiles. Most of the time you will
|
||||
want to answer (y)es here.</para></listitem>
|
||||
|
||||
<listitem><para>Copies the <filename>INDEX</filename> from the <filename>ports</filename> directory to the
|
||||
<filename>gen</filename> directory. In doing so it removes the lines for ports
|
||||
<listitem><para>Copies the <filename>INDEX</filename> from the
|
||||
<filename>ports</filename> directory to the <filename>gen</filename>
|
||||
directory. In doing so it removes the lines for ports
|
||||
where the packages do not exist. It also checks to make sure
|
||||
that all of the required dependency packages are
|
||||
present.</para></listitem>
|
||||
|
@ -301,9 +302,9 @@
|
|||
<Filename>oneshot.pl</filename> and re-run
|
||||
<command>./doit.sh</command>. The second and subsequent times
|
||||
around it will skip steps 1-5 above. If you want to re-run any
|
||||
of those steps refer to <filename>doit.sh</filename> for which files need to be
|
||||
removed to not short-circuit those steps. If you want to repeat
|
||||
all of these steps then the easiest way is to <command>rm -rf
|
||||
of those steps refer to <filename>doit.sh</filename> for which files
|
||||
need to be removed to not short-circuit those steps. If you want to
|
||||
repeat all of these steps then the easiest way is to <command>rm -rf
|
||||
gen</command>.</para>
|
||||
|
||||
<para>Upon successful completion the packages/distfiles will be in
|
||||
|
@ -320,8 +321,8 @@
|
|||
<listitem><para>This is a pretty common occurrence. You will
|
||||
either need to wait for a new set of packages where the
|
||||
missing packages were built or get someone to re-start the
|
||||
package build for you. <emphasis>Do not</emphasis> attempt to build the missing
|
||||
packages on your own machine and add them into the fray.
|
||||
package build for you. <emphasis>Do not</emphasis> attempt to build
|
||||
the missing packages on your own machine and add them into the fray.
|
||||
While you might be able to get away with this if you are
|
||||
extremely careful the vast majority of the time you will miss
|
||||
some little detail and the simple process of adding a
|
||||
|
@ -333,11 +334,12 @@
|
|||
<term>Required packages will not fit</term>
|
||||
|
||||
<listitem><para>This happens on occasion too and is relatively
|
||||
easy to fix. Simply edit <filename>print-cdrom-packages.sh</filename> to move
|
||||
easy to fix. Simply edit
|
||||
<filename>print-cdrom-packages.sh</filename> to move
|
||||
packages around until they fit. Yes this is an iterative
|
||||
process and one of the reasons why you should enable <varname>fake</varname> in
|
||||
<filename>oneshot.pl</filename> until you have gotten
|
||||
things the way you want them. Re-run
|
||||
process and one of the reasons why you should enable
|
||||
<varname>fake</varname> in <filename>oneshot.pl</filename> until you
|
||||
have gotten things the way you want them. Re-run
|
||||
<command>./doit.sh</command> after you made your
|
||||
adjustments.</para></listitem>
|
||||
</varlistentry>
|
||||
|
|
Loading…
Reference in a new issue