os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Now that the Handbook knows how to cut a release, point there instead

Browse source 
of having tutorial in the FAQ.

This commit affects two FAQs; the original tutorial, and one that
pointed at that tutorial.
This commit is contained in:
Michael Lucas 2002-01-28 15:16:59 +00:00
parent a418d0e31b
commit 3579b70726
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11943
1 changed files with 5 additions and 59 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

64
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -1238,8 +1238,8 @@ File: +DESC (ignored)</screen>
release, which will include your install floppy.</para>
<para>To make a custom release, follow the instructions
<link linkend="custrel">in the Advanced Topics section of
the FAQ</link>.</para>
<ulink url="../handbook/custom-release.html">in the Making
your Own Release</ulink> section of the Handbook.</para>
</answer>
</qandaentry>
@ -11829,63 +11829,9 @@ raisechar=^^</programlisting>
</question>
<answer>
<para>To make a release you need to do three things: First,
you need to be running a kernel with the
&man.vn.4;
driver configured in. Add this to your kernel config file
and build a new kernel:</para>
<programlisting>pseudo-device vn #Vnode driver (turns a file into a device)</programlisting>
<para>Second, you have to have the whole CVS repository at
hand. To get this you can use <ulink
URL="../handbook/synching.html#CVSUP">CVSUP</ulink> but in
your supfile set the release name to cvs and remove any tag or
date fields:</para>
<programlisting>*default prefix=/home/ncvs
*default base=/a
*default host=cvsup.FreeBSD.org
*default release=cvs
*default delete compress use-rel-suffix
## Main Source Tree
src-all
# Other stuff
ports-all
www
doc-all</programlisting>
<para>Then run <command>cvsup -g supfile</command> to suck all
the good bits onto your box...</para>
<para>Finally, you need a chunk of empty space to build into.
Let us say it is in <filename>/some/big/filesystem</filename>,
and from the example above you have got the CVS repository in
<filename>/home/ncvs</filename>:</para>
<screen>&prompt.root; <userinput>setenv CVSROOT /home/ncvs</userinput> # or export CVSROOT=/home/ncvs
&prompt.root; <userinput>cd /usr/src</userinput>
&prompt.root; <userinput>make buildworld</userinput>
&prompt.root; <userinput>cd /usr/src/release</userinput>
&prompt.root; <userinput>make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release</userinput></screen>
<note>
<para>Please note that you <emphasis>do not</emphasis>
need to build world if you already have a populated
<filename>/usr/obj</filename>.</para>
</note>
<para>An entire release will be built in
<filename>/some/big/filesystem/release</filename> and you
will have a full FTP-type installation in
<filename>/some/big/filesystem/release/R/ftp</filename> when
you are done. If you want to build your SNAP along some other
branch than -CURRENT, you can also add
<literal>RELEASETAG=SOMETAG</literal> to the make release
command line above, e.g. <literal>RELEASETAG=RELENG_2_2</literal>
would build an up-to-the- minute 2.2-STABLE snapshot.</para>
<para>Please see the <ulink
url="../handbook/custom-release.html">Making your Own
Release</ulink> section of the Handbook.</para>
</answer>
</qandaentry>