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

Diff for /www/Attic/ports.html between version 1.46 and 1.47

version 1.46, 2000/12/18 03:21:41 version 1.47, 2001/02/18 15:23:35
Line 1 
Line 1 
   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
 <html>  <html>
 <head>  <head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <meta name="resource-type" content="document">  <meta name="resource-type" content="document">
 <meta name="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">  <meta name="description" content="The OpenBSD Ports and Packages Collection">
 <meta name="keywords" content="openbsd,ports">  <meta name="keywords" content="openbsd,ports">
 <meta name="distribution" content="global">  <meta name="distribution" content="global">
 <meta name="copyright" content="copyright 1997-1999 by the OpenBSD project">  <meta name="copyright" content="copyright 1997-2001 by the OpenBSD project">
 <title>OpenBSD Ports and Packages</title>  <title>OpenBSD Ports and Packages</title>
 <link rev="made" HREF="mailto:www@openbsd.org">  <link rev="made" href="mailto:www@openbsd.org">
 </head>  </head>
   
 <body text="#000000" bgcolor="#FFFFFF" link="#23238E">  <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
   
 <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >  <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >
   
 <h2><font color=#e00000>The Ports &amp; Packages collection</font><hr></h2>  <h2><font color="#e00000">The Ports &amp; Packages collection</font></h2>
   
 <h3><font color=#0000e0>Motivation</font></h3>  <hr>
   
   <h3><font color="#0000e0">Motivation</font></h3>
   
 OpenBSD is a fairly complete system of its own, but still there is a lot  OpenBSD is a fairly complete system of its own, but still there is a lot
 of software that one might want see added. However there is the problem  of software that one might want see added. However there is the problem
 on where to draw the line as to what to include, as well as the occasional  on where to draw the line as to what to include, as well as the occasional
Line 26 
Line 29 
 shipped with the system.  shipped with the system.
   
 <p>  <p>
 <strong><font color=#e00000>  <strong><font color="#e00000">
 The ports &amp; packages collection does NOT go through the thorough security audit that OpenBSD follows.  The ports &amp; packages collection does NOT go through the thorough security audit that OpenBSD follows.
 Although we strive to keep the quality of the packages collection high, we just do not have enough human  Although we strive to keep the quality of the packages collection high, we just do not have enough human
 resources to ensure the same level of robustness and security.  resources to ensure the same level of robustness and security.
Line 52 
Line 55 
 a package that can be registered into the system using pkg_add(1).  a package that can be registered into the system using pkg_add(1).
   
 <p>  <p>
 <strong><font color=#e00000>  <strong><font color="#e00000">
 Packages look like simple <code>.tgz</code> bundles, but they should  Packages look like simple <code>.tgz</code> bundles, but they should
 always be added using  always be added using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>,  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&amp;sektion=1&amp;format=html">pkg_add(1)</a>,
 as there might be some extra information that only  as there might be some extra information that only
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&amp;sektion=1&amp;format=html">pkg_add(1)</a>
 knows how to handle.</font></strong>  knows how to handle.</font></strong>
 Tip: you can distinguish between packages and <strong>.tgz</strong> bundles  Tip: you can distinguish between packages and <strong>.tgz</strong> bundles
 using  using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a>.  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&amp;sektion=1&amp;format=html">pkg_info(1)</a>.
   
 <h3><font color=#0000e0>Getting packages</font></h3>  <h3><font color="#0000e0">Getting packages</font></h3>
   
 A large collection of pre-compiled packages is available for most common  A large collection of pre-compiled packages is available for most common
 architectures.  architectures.
Line 92 
Line 95 
     # pkg_add ${PKG_PATH}gimp-1.1.27.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>  <h3><a name="stable"><font color="#0000e0">Ports and packages update for an OpenBSD release</font></a></h3>
 <p>  <p>
 The 2.7 release saw the introduction of a stable branch for the ports tree.  The 2.7 release saw the introduction of a stable branch for the ports tree.
 <p>  <p>
Line 116 
Line 119 
 and a bug-fixed package.  and a bug-fixed package.
 </p>  </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&amp;sektion=7&amp;format=html">packages(7)</a>
 manual page holds useful information about ways to manage  manual page holds useful information about ways to manage
 installed packages, solve conflicts (files that already exist) and handle  installed packages, solve conflicts (files that already exist) and handle
 dependencies.  dependencies.
Line 126 
Line 129 
 As of OpenBSD 2.8, 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&amp;sektion=1&amp;format=html">pkg_delete(1)</a>
 <li>Add the new package using  <li>Add the new package using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&amp;sektion=1&amp;format=html">pkg_add(1)</a>
 </ul>  </ul>
 This is slightly inconvenient, as packages may trigger dependencies, and  This is slightly inconvenient, as packages may trigger dependencies, and
 you may have to remove a large subset of packages for an update.  you may have to remove a large subset of packages for an update.
   
 <h3><font color=#0000e0>Using ports</font></h3>  <h3><font color="#0000e0">Using ports</font></h3>
   
 If a given package does not exist for your architecture, you may still  If a given package does not exist for your architecture, you may still
 be able to compile the port. Besides, some users will want to compile  be able to compile the port. Besides, some users will want to compile
Line 146 
Line 149 
 The release versions are the ones we ship on our CDROM, and have gone  The release versions are the ones we ship on our CDROM, and have gone
 through more testing than any snapshot.  through more testing than any snapshot.
 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&amp;sektion=7&amp;format=html">ports(7)</a> man page.
   
 <h3><font color=#0000e0>Life cycle of the ports tree</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 160 
Line 163 
 release.  release.
 </ul>  </ul>
 The change of status will be widely publicized on the  The change of status will be widely publicized on the
 <a href=mail.html>Mailing lists</a>.  <a href=mail.html>mailing lists</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
Line 173 
Line 176 
 It is strongly suggested that people don't track ports-current unless  It is strongly suggested that people don't track ports-current unless
 they're prepared to deal with various problems.  they're prepared to deal with various problems.
 <a href=mail.html>Mailing lists</a> such as  <a href=mail.html>Mailing lists</a> such as
 <code>source-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>A list of <a href="portsplus.html">daily changes</a> to ports
   and ports-current is available.
   
 <p>  <p>
 The ports-current tree can be retrieved via:  The ports-current tree can be retrieved via:
 <ul>  <ul>
Line 192 
Line 198 
         web interface</a>.          web interface</a>.
 </ul>  </ul>
   
 <h3><font color=#0000e0>Ports and XFree</font></h3>  <h3><font color="#0000e0">Ports and XFree</font></h3>
 There is some special magic in the OpenBSD XFree configuration files  There is some special magic in the OpenBSD XFree configuration files
 that allows the ports tree to install imake-based applications under  that allows the ports tree to install imake-based applications under
 /usr/local.  /usr/local.
Line 205 
Line 211 
 ports tree.  ports tree.
 <p>Future releases of XFree 4.0.x will probably include the necessary magic.  <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>
   
 <p>  <p>
 Let's say you managed to get a ports tree and you want to compile and  Let's say you managed to get a ports tree and you want to compile and
Line 246 
Line 252 
 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.
   
 <h3><font color=#0000e0>Creating new ports</font></h3>  <h3><font color="#0000e0">Creating new ports</font></h3>
 <p>  <p>
 If you are interested in helping to expand the OpenBSD ports tree  If you are interested in helping to expand the OpenBSD ports tree
 you should first read <a href="porting.html">porting.html</a>.  you should first read <a href="porting.html">porting.html</a>.
Line 254 
Line 260 
 <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>  <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
 as well as OpenBSD specific policies and hints.  as well as OpenBSD specific policies and hints.
   
 <h3><font color=#0000e0>Problems and contacts</font></h3>  <h3><font color="#0000e0">Problems and contacts</font></h3>
   
 <p>  <p>
 If you have trouble with existing ports, or need information about creating new ports,  If you have trouble with existing ports, or need information about creating new ports,
Line 270 
Line 276 
 always required. Some ports may have configuration issues linked to what  always required. Some ports may have configuration issues linked to what
 is already on your machine.  is already on your machine.
 <ul>  <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>Use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=script&amp;sektion=1&amp;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>Attach the output of <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&amp;sektion=1&amp;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      <li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc&amp;sektion=1&amp;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  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>.  provide at least the various files produced by <tt>gcc -save-temps</tt>.
 </ul>  </ul>
   
 <hr>  <hr>
 <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>  <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>  <a href="mailto:www@openbsd.org">www@openbsd.org</a>
 <br><small>$OpenBSD$</small>  <br><small>$OpenBSD$</small>
 </body>  </body>
 </html>  </html>
Legend:
Removed from v.1.46  
changed lines
  Added in v.1.47