The package-splitting scripts now live in CVS (and have for some
time). Point users to the right location in the ports tree. Also adjust certain pathname references to reflect reality. Inspired by: talk(1) session with will
This commit is contained in:
parent
8f0091346e
commit
bcaf2d3374
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=13903
1 changed files with 16 additions and 22 deletions
|
@ -107,20 +107,14 @@
|
||||||
those package sets for the official FreeBSD release
|
those package sets for the official FreeBSD release
|
||||||
discs.</para>
|
discs.</para>
|
||||||
|
|
||||||
<para>First off you'll need to get a copy of the tarball from the
|
<para>The scripts and other files needed to produce a package
|
||||||
following URL :</para>
|
split can be found in the CVS tree in
|
||||||
|
<filename>ports/Tools/scripts/release</filename>.
|
||||||
<para><ulink
|
Copy this directory to a machine that has enough free HD
|
||||||
url="http://people.freebsd.org/~steve/release-scripts.tgz"></ulink></para>
|
|
||||||
|
|
||||||
<para>Copy this archive to a machine that has enough free HD
|
|
||||||
space to hold 2 to 3 times the size of the package set that you
|
space to hold 2 to 3 times the size of the package set that you
|
||||||
wish to split. The tarball will extract into the current
|
wish to split.</para>
|
||||||
working directory so make sure you have created one suitably named
|
|
||||||
directory for the release you are working on.</para>
|
|
||||||
|
|
||||||
<para>After you have extracted the files, you will notice the
|
<para>The following scripts are present in this directory:</para>
|
||||||
following files :</para>
|
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -153,7 +147,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>scripts/checkdeps.pl</filename></term>
|
<term><filename>checkdeps.pl</filename></term>
|
||||||
|
|
||||||
<listitem><para>Makes sure all packages dependencies are
|
<listitem><para>Makes sure all packages dependencies are
|
||||||
satisfied given an INDEX file and a directory of
|
satisfied given an INDEX file and a directory of
|
||||||
|
@ -161,7 +155,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>scripts/oneshot.pl</filename></term>
|
<term><filename>oneshot.pl</filename></term>
|
||||||
|
|
||||||
<listitem><para>This is where all the magic (and I use that
|
<listitem><para>This is where all the magic (and I use that
|
||||||
term loosely as it is mostly just a brute force approach)
|
term loosely as it is mostly just a brute force approach)
|
||||||
|
@ -172,7 +166,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>scripts/print-cdrom-packages.sh</filename></term>
|
<term><filename>print-cdrom-packages.sh</filename></term>
|
||||||
|
|
||||||
<listitem><para>This file is a copy of
|
<listitem><para>This file is a copy of
|
||||||
<filename>src/release/scripts/print-cdrom-packages.sh</filename>
|
<filename>src/release/scripts/print-cdrom-packages.sh</filename>
|
||||||
|
@ -180,7 +174,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>scripts/scrubindex.pl</filename></term>
|
<term><filename>scrubindex.pl</filename></term>
|
||||||
|
|
||||||
<listitem><para>This script removes lines from an INDEX file
|
<listitem><para>This script removes lines from an INDEX file
|
||||||
for packages that aren't present. It also removes the
|
for packages that aren't present. It also removes the
|
||||||
|
@ -190,7 +184,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>scripts/setup.sh</filename></term>
|
<term><filename>setup.sh</filename></term>
|
||||||
|
|
||||||
<listitem><para>This is a helper script that I use on the
|
<listitem><para>This is a helper script that I use on the
|
||||||
bento cluster to grab a copy of the ports tree and the
|
bento cluster to grab a copy of the ports tree and the
|
||||||
|
@ -216,7 +210,7 @@
|
||||||
fake the copying of packages and distfiles. This will save
|
fake the copying of packages and distfiles. This will save
|
||||||
both time and diskspace while you do a couple of trial runs to
|
both time and diskspace while you do a couple of trial runs to
|
||||||
make sure things fit, etc. In the
|
make sure things fit, etc. In the
|
||||||
<filename>scripts/oneshot.pl</filename> set the fake variable
|
<filename>oneshot.pl</filename> set the fake variable
|
||||||
to 1 and instead of actually copying the files it will
|
to 1 and instead of actually copying the files it will
|
||||||
&man.touch.1; them. Be sure you turn this off or set fake to
|
&man.touch.1; them. Be sure you turn this off or set fake to
|
||||||
0 before you give the resultant discs to the person that will
|
0 before you give the resultant discs to the person that will
|
||||||
|
@ -228,7 +222,7 @@
|
||||||
from the correct release.</para></listitem>
|
from the correct release.</para></listitem>
|
||||||
|
|
||||||
<listitem><para>Check to make sure the XFree86 dependency in
|
<listitem><para>Check to make sure the XFree86 dependency in
|
||||||
<filename>scripts/scrubindex.pl</filename> has the correct
|
<filename>scrubindex.pl</filename> has the correct
|
||||||
version number. You'll also need to make sure this value is
|
version number. You'll also need to make sure this value is
|
||||||
correct in <filename>doit.sh</filename> as
|
correct in <filename>doit.sh</filename> as
|
||||||
well.</para></listitem>
|
well.</para></listitem>
|
||||||
|
@ -236,7 +230,7 @@
|
||||||
|
|
||||||
<para>Next you'll need to get a copy of the ports tree, packages,
|
<para>Next you'll need to get a copy of the ports tree, packages,
|
||||||
and distfiles from a recent build on the package cluster. See
|
and distfiles from a recent build on the package cluster. See
|
||||||
the <filename>scripts/setup.sh</filename> for a working example
|
the <filename>setup.sh</filename> for a working example
|
||||||
but essentially here's what needs to be done.</para>
|
but essentially here's what needs to be done.</para>
|
||||||
|
|
||||||
<orderedlist>
|
<orderedlist>
|
||||||
|
@ -304,7 +298,7 @@
|
||||||
<para>After going through this the first time if you are lucky
|
<para>After going through this the first time if you are lucky
|
||||||
enough that all of the required packages built and fit on each
|
enough that all of the required packages built and fit on each
|
||||||
disc. All you need to do is set fake to 0 in
|
disc. All you need to do is set fake to 0 in
|
||||||
<Filename>scripts/oneshot.pl</filename> and re-run
|
<Filename>oneshot.pl</filename> and re-run
|
||||||
<command>./doit.sh</command>. The second and subsequent times
|
<command>./doit.sh</command>. The second and subsequent times
|
||||||
around it will skip steps 1-5 above. If you want to re-run any
|
around it will skip steps 1-5 above. If you want to re-run any
|
||||||
of those steps refer to doit.sh for which files need to be
|
of those steps refer to doit.sh for which files need to be
|
||||||
|
@ -342,7 +336,7 @@
|
||||||
easy to fix. Simply edit print-cdrom-packages.sh to move
|
easy to fix. Simply edit print-cdrom-packages.sh to move
|
||||||
packages around until they fit. Yes this is an iterative
|
packages around until they fit. Yes this is an iterative
|
||||||
process and one of the reasons why you should enable fake in
|
process and one of the reasons why you should enable fake in
|
||||||
<filename>scripts/oneshot.pl</filename> until you have gotten
|
<filename>oneshot.pl</filename> until you have gotten
|
||||||
things the way you want them. Re-run
|
things the way you want them. Re-run
|
||||||
<command>./doit.sh</command> after you made your
|
<command>./doit.sh</command> after you made your
|
||||||
adjustments.</para></listitem>
|
adjustments.</para></listitem>
|
||||||
|
|
Loading…
Reference in a new issue