===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- www/Attic/ports.html	2000/08/21 12:57:59	1.36
+++ www/Attic/ports.html	2000/09/07 22:19:45	1.37
@@ -132,6 +132,25 @@
 The change of status will be widely publicized on the 
 <a href=mail.html>Mailing lists</a>.
 
+<p>
+The current ports tree <strong>may not</strong> be used with the previous
+release once the switch to tracking OpenBSD-current occurs.  This is due
+to changes, typically with the port make process, that require code
+based upon the OpenBSD-current source tree.   To get the latest version of
+the ports tree that will work with the previous release:
+<ul>
+<li>Determine the cut-off date.   Example, the cut-off between 2.7 and
+    2.8 was indicated by a message to ports@openbsd.org on Aug 16, 2000.
+<li>Check out a version of the ports tree as of the cut-off date.  The
+    steps are (assuming your ports tree came from anoncvs and live in
+    /usr/ports):
+<pre>
+    $ cd /usr/ports
+    $ cvs -q -d anoncvs@some.anon.server:/cvs up -D 08/15/00 -Pd
+</pre>
+    Change the name of the server and cut-off date to fit your needs.
+</ul>
+
 <p>The ports tree works as a single entity. Updating a single directory is
 not guaranteed to work, as package dependencies may force you to update
 and recompile vast portions of the ports tree.
@@ -234,6 +253,6 @@
 <hr>
 <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>
-<br><small>$OpenBSD: ports.html,v 1.36 2000/08/21 12:57:59 brad Exp $</small>
+<br><small>$OpenBSD: ports.html,v 1.37 2000/09/07 22:19:45 marc Exp $</small>
 </body>
 </html>