faq5.html - # unset RELEASEDIR DESTDIR

comet <[email protected]>
Newsgroups gmane.os.openbsd.www
Message-ID <CAJZt+JWMUg4L+aaVfroZQHYwYNJmQp60=Z8hR4H3a9fCuVFwtg@mail.gmail.com>
While building OpenBSD 5.1-stable I had much trouble that could have
been avoided if the FAQ specified one little detail about the release
process:

# unset RELEASEDIR DESTDIR

It also might have helped had I read the manual for release(8).

Here is a link to a discussion of my troubles in Daemonforums:

http://www.daemonforums.org/showthread.php?t=7125

My proposal to FAQ5 includes moving the reference to the release(8) manual up
to just after the <h3>Doing a Release</h3> phrase.

And to include this command in the release process:
    # unset RELEASEDIR DESTDIR

Index: faq5.html
===================================================================
RCS file: /cvs/www/faq/faq5.html,v
retrieving revision 1.192
diff -u -r1.192 faq5.html
--- faq5.html   1 May 2012 14:35:14 -0000       1.192
+++ faq5.html   18 May 2012 03:46:24 -0000
@@ -777,7 +777,10 @@

 <p>
 <h3>Doing a release</h3>
+The authoritative instructions on making a release are in
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=release&amp;sektion=8">release(8)</a>.

+<p>
 Define our DESTDIR and RELEASEDIR environment variables:
 <blockquote><pre>
 # <b>export DESTDIR=/usr/dest</b>
@@ -811,13 +814,17 @@
 # <b>sh checkflist</b>
 </pre></blockquote>

+<p>
+Undefine our DESTDIR and RELEASEDIR environment variables as these can
+get in the way of other build processes:
+
+<blockquote><pre>
+# <b>unset RELEASEDIR DESTDIR</b>
+</pre></blockquote>
+
 You now have complete and checked release file sets in the RELEASEDIR.
 These files can now be used to install or upgrade OpenBSD on other
 machines.
-
-<p>
-The authoritative instructions on making a release are in
-<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=release&amp;sektion=8">release(8)</a>.

 <p>
 Note: if you wish to distribute the resultant files by HTTP for use by
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.