[BACK]Return to ports.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/Attic/ports.html between version 1.58 and 1.59

version 1.58, 2001/09/10 19:26:32 version 1.59, 2001/10/06 14:00:36
Line 174 
Line 174 
   
 <p>  <p>
 The ports tree, like the rest of OpenBSD, is constantly changing.  The ports tree, like the rest of OpenBSD, is constantly changing.
 The normal life cycle of the ports tree is as follows:  
 <ul>  
 <li>Track the latest release of OpenBSD for a few months after the release  
 comes out.  
 <li>Switch to tracking OpenBSD-current about two months before the next  
 release.  
 </ul>  
 The change of status will be widely publicized on the  
 <a href=mail.html>mailing lists</a>. As of OpenBSD 2.9, the ports  
 tree also gets tagged before the switch. If you're running a <i>stable</i>  
 system, you can update to the last `correct' experimental ports tree that  
 works on your system as follows:  
 <pre>  
         # <strong>cvs -q up -rOPENBSD_2_9_TRACKING_SWITCH -P ports</strong>  
 </pre>  
 For definitions of <i>current</i> and <i>stable</i>, see the  
 <a href="faq/upgrade-minifaq.html#1.1">Upgrade  
 Mini-FAQ</a>.  
   
 <p>  <p>
 The current ports tree <strong>may not</strong> be used with the previous  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  release.  This is due to changes, typically with the port make process,
 to changes, typically with the port make process, that require code  that require code based upon the OpenBSD-current source tree.
 based upon the OpenBSD-current source tree. This switch will be announced  
 on the <a href="mail.html"><tt>ports@openbsd.org</tt> mailing list</a>.  
 <p>The ports tree works as a single entity. Updating a single directory is  <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  not guaranteed to work, as package dependencies may force you to update
 and recompile vast portions of the ports tree.  and recompile vast portions of the ports tree.
Line 207 
Line 186 
 <a href=mail.html>Mailing lists</a> such as  <a href=mail.html>Mailing lists</a> such as
 <code>ports-changes@openbsd.org</code> or  <code>ports-changes@openbsd.org</code> or
 <code>tech@openbsd.org</code> will probably be invaluable.  <code>tech@openbsd.org</code> will probably be invaluable.
   
   <p>You are advised to track ports-stable on a production machine:
   we will try to keep the stable ports tree up-to-par with respect to
   problems, and to provide timely binary updates as well.
   
   <p>Note that vanishing distfiles is not an issue, as
   ftp.openbsd.org holds the complete repository. Even changing checksums is
   not an issue: you can issue the command
   <pre>
           make checksum REFETCH=true
   </pre>
   to make sure you are grabbing the correct distfile for your ports tree.
   
   For definitions of <i>current</i> and <i>stable</i>, see the
   <a href="faq/upgrade-minifaq.html#1.1">Upgrade
   Mini-FAQ</a>.
   
   
 <p>A list of <a href="portsplus/index.html">daily changes</a> to ports  <p>A list of <a href="portsplus/index.html">daily changes</a> to ports
 and ports-current is available.  and ports-current is available.
Legend:
Removed from v.1.58  
changed lines
  Added in v.1.59