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

Diff for /www/Attic/ports.html between version 1.44 and 1.45

version 1.44, 2000/12/13 17:30:54 version 1.45, 2000/12/18 00:49:11
Line 77 
Line 77 
 </ul>  </ul>
 </ul>  </ul>
   
 <p>  
 As of the 2.8 release, there is a stable ports tree branch, similar to  
 what source stable is. Please refer to the  
 <a href="pkg-stable.html">stable packages page</a> to find out about  
 updated packages.  
 </p>  
   
 Adding a package is as easy as  Adding a package is as easy as
 <code>pkg_add pkgname.tgz</code>.  <code>pkg_add pkgname.tgz</code>.
Line 90 
Line 84 
 set PKG_PATH to that repository URL, in order to grab dependencies.  set PKG_PATH to that repository URL, in order to grab dependencies.
   
 <p>  <p>
 For instance, to install the gimp package for the 2.7 release on an i386  For instance, to install the gimp package for the 2.8 release on an i386
 machine off the ftp site (including dependencies), do:  machine off the ftp site (including dependencies), do:
   
 <pre>  <pre>
     # setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/      # setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.8/packages/i386/
     # pkg_add ${PKG_PATH}gimp-1.1.17.tgz      # pkg_add ${PKG_PATH}gimp-1.1.27.tgz
 </pre>  </pre>
   
   <h3><font color=#0000e0>Ports and packages update for an OpenBSD release</font></h3>
   <p>
   The 2.7 release saw the introduction of a stable branch for the ports tree.
   <p>
   For instance, to grab the stable branch for the 2.8 release:
   <pre>
       $ cd /usr/ports
       $ cvs -q -d anoncvs@some.anon.server:/cvs up -r OPENBSD_2_8 -Pd
   </pre>
   <p>
   Starting with the 2.8 release, selected binary packages are also made
   available.  Please refer to the
   <a href="pkg-stable.html">stable packages page</a> to find out about
   updated packages and important updates to the stable branch.
   </p>
   <p>
   Package names are <strong>always</strong> changed in case of a package
   update, to avoid any risk of confusion between a package from the release
   and a bug-fixed package.
   </p>
   
 <h3><font color=#0000e0>Managing installed packages</font></h3>  <h3><font color=#0000e0>Managing installed packages</font></h3>
   
 The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>  The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>
Line 105 
Line 120 
 installed packages, solve conflicts (files that already exist) and handle  installed packages, solve conflicts (files that already exist) and handle
 dependencies.  dependencies.
 <p>  <p>
 As of OpenBSD 2.7, to update a package you must:  As of OpenBSD 2.8, to update a package you must:
 <ul>  <ul>
 <li>Remove the old package using  <li>Remove the old package using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a>  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a>
Line 130 
Line 145 
 Further information is available in the  Further information is available in the
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">ports(7)</a> man page.  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">ports(7)</a> man page.
   
 <h3><font color=#0000e0>Ports update for an OpenBSD release</font></h3>  <h3><font color=#0000e0>Life cycle of the ports tree</font></h3>
   
 <p>  <p>
 The ports tree, like the rest of OpenBSD, is constantly changing.  The ports tree, like the rest of OpenBSD, is constantly changing.
Line 148 
Line 163 
 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 once the switch to tracking OpenBSD-current occurs.  This is due
 to changes, typically with the port make process, that require code  to changes, typically with the port make process, that require code
 based upon the OpenBSD-current source tree.   To get the latest version of  based upon the OpenBSD-current source tree.
 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 that build with the 2.7 release have also been put into a  
 branch of their own.  Instead of grabbing the ports by date you can:  
 <pre>  
     $ cd /usr/ports  
     $ cvs -q -d anoncvs@some.anon.server:/cvs up -r OPENBSD_2_7 -Pd  
 </pre>  
 The OPENBSD_2_7 tag does not imply these ports are in any way `stable', only  
 that the ports will build on a 2.7 system.  Security fixes may be added  
 to this branch.  
 <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 203 
Line 195 
 /usr/local.  /usr/local.
   
 <p>OpenBSD currently does not ship with XFree 4.0.x for various reasons.  <p>OpenBSD currently does not ship with XFree 4.0.x for various reasons.
 This ports magic does not work with the XFree 4.0.x distribution.  This ports magic does not work with the XFree 4.0.x distribution (yet).
 You will need to apply the patch in  You will need to apply the patch in
 <code>/usr/ports/infrastructure/patches/patch-xfree-4.0</code>  <code>/usr/ports/infrastructure/patches/patch-xfree-4.0</code>
 to a default binary XFree 4.0.x distribution for it to work with the OpenBSD  to a default binary XFree 4.0.x distribution for it to work with the OpenBSD
 ports tree.  ports tree.
   <p>Future releases of XFree 4.0.x will probably include the necessary magic.
   
 <h3><font color=#0000e0>Example use of the Ports tree</font></h3>  <h3><font color=#0000e0>Example use of the Ports tree</font></h3>
   
Line 236 
Line 229 
 </ul>  </ul>
   
 <p>  <p>
 In OpenBSD 2.7, a large proportion of the ports automatically build  With OpenBSD 2.8, almost all ports automatically build
 packages when installing.  packages when installing.
 In OpenBSD current, almost all ports follow that standard.  
   
 <p>  <p>
 As ports get built, the /usr/ports/distfiles directory gets filled with  As ports get built, the /usr/ports/distfiles directory gets filled with
 program sources, and /usr/ports/packages gets filled with binary packages.  program sources, and /usr/ports/packages gets filled with binary packages.
 Users with low connectivity may refer to mirror-distfiles(7) for  Users with low connectivity may refer to mirror-distfiles(7) for
 an efficient way to grab all distfiles at once.  an efficient way to grab all distfiles at once.  In OpenBSD-current, you
   can use the script /usr/ports/infrastructure/fetch/clean-old to remove
   track distfiles.
 Note that the OpenBSD CD only include the ports tree and selected packages.  Note that the OpenBSD CD only include the ports tree and selected packages.
 If you wish to have the distfiles, you will have to get them through an  If you wish to have the distfiles, you will have to get them through an
 independent way.  independent way.
Line 268 
Line 262 
 <li>The output of <code>uname -a</code>,  <li>The output of <code>uname -a</code>,
 <li>Your OpenBSD version, including any patches you may have applied,  <li>Your OpenBSD version, including any patches you may have applied,
 <li>A complete description of the problem.  <li>A complete description of the problem.
   </ul>
   For ports that don't build correctly, a complete build transcript is almost
   always required. Some ports may have configuration issues linked to what
   is already on your machine.
   <ul>
   <li>Use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=script&sektion=1&format=html">script(1)</a> to create a complete build transcript. Don't remove the configure information.
       <li>Attach the output of <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a> if it seems even remotely relevant.
       <li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc&sektion=1&format=html">gcc(1)</a> internal  compiler errors do ask you to report the bug to
   the gcc mailing-list. It does save time if you follow their direction, and
   provide at least the various files produced by <tt>gcc -save-temps</tt>.
 </ul>  </ul>
   
 <hr>  <hr>
Legend:
Removed from v.1.44  
changed lines
  Added in v.1.45