Annotation of www/ports.html, Revision 1.44
1.11 deraadt 1: <html>
1.25 deraadt 2: <head>
3: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
4: <meta name="resource-type" content="document">
5: <meta name="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">
6: <meta name="keywords" content="openbsd,ports">
7: <meta name="distribution" content="global">
8: <meta name="copyright" content="copyright 1997-1999 by the OpenBSD project">
1.27 brad 9: <title>OpenBSD Ports and Packages</title>
1.25 deraadt 10: <link rev="made" HREF="mailto:www@openbsd.org">
1.43 jufi 11: </head>
1.25 deraadt 12:
13: <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
14:
15: <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >
1.30 espie 16:
1.31 espie 17: <h2><font color=#e00000>The Ports & Packages collection</font><hr></h2>
1.25 deraadt 18:
1.31 espie 19: <h3><font color=#0000e0>Motivation</font></h3>
1.25 deraadt 20:
21: OpenBSD is a fairly complete system of its own, but still there is a lot
22: of software that one might want see added. However there is the problem
23: on where to draw the line as to what to include, as well as the occasional
24: licensing and export restriction problems. As OpenBSD is supposed to be
25: a small stand-alone UNIX-like operating system, some things just can't be
26: shipped with the system.
27:
28: <p>
1.31 espie 29: <strong><font color=#e00000>
30: The ports & packages collection does NOT go through the thorough security audit that OpenBSD follows.
31: Although we strive to keep the quality of the packages collection high, we just do not have enough human
32: resources to ensure the same level of robustness and security.
33: </font></strong>
1.25 deraadt 34:
35: <p>
1.31 espie 36: The port collection, originally borrowed from
37: <a href="http://www.freebsd.org/">FreeBSD</a>, fills this gap.
38: The concept is to have, for each third-party software, a Makefile that
1.25 deraadt 39: controls
40: <ul>
41: <li>where to fetch it,
42: <li>how to do the fetch,
43: <li>what it depends upon (if anything),
44: <li>how to alter the sources (if needed),
45: <li>and how to configure, build and install it.
46: </ul>
47: This information is kept in a directory hierarchy under the
48: /usr/ports directory.
1.31 espie 49:
50: <p>
51: Packages are the binary equivalent of ports. A compiled port becomes
52: a package that can be registered into the system using pkg_add(1).
53:
54: <p>
55: <strong><font color=#e00000>
1.36 brad 56: Packages look like simple <code>.tgz</code> bundles, but they should
1.33 espie 57: always be added using
58: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>,
59: as there might be some extra information that only
60: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
61: knows how to handle.</font></strong>
1.36 brad 62: Tip: you can distinguish between packages and <strong>.tgz</strong> bundles
1.33 espie 63: using
64: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a>.
1.31 espie 65:
66: <h3><font color=#0000e0>Getting packages</font></h3>
67:
68: A large collection of pre-compiled packages is available for most common
69: architectures.
70: <ul>
1.34 jufi 71: <li>On the CD-Rom (that you can order <a href="orders.html">here</a>),
1.31 espie 72: <li>On the <a href=ftp.html>ftp mirror sites</a>.
1.40 beck 73: <li>Browsed and retrieved from the web package lists:
74: <ul>
1.44 ! espie 75: <li><a href="http://www.openbsd.org/2.8_packages/">Packages for OpenBSD 2.8</a>
1.42 jufi 76: <li><a href="http://www.openbsd.org/2.7_packages/">Packages for OpenBSD 2.7</a>
1.40 beck 77: </ul>
1.31 espie 78: </ul>
79:
1.44 ! espie 80: <p>
! 81: As of the 2.8 release, there is a stable ports tree branch, similar to
! 82: what source stable is. Please refer to the
! 83: <a href="pkg-stable.html">stable packages page</a> to find out about
! 84: updated packages.
! 85: </p>
! 86:
1.31 espie 87: Adding a package is as easy as
1.36 brad 88: <code>pkg_add pkgname.tgz</code>.
1.31 espie 89: If you are grabbing packages off a single source (a package repository),
1.39 espie 90: set PKG_PATH to that repository URL, in order to grab dependencies.
1.31 espie 91:
92: <p>
93: For instance, to install the gimp package for the 2.7 release on an i386
94: machine off the ftp site (including dependencies), do:
95:
96: <pre>
97: # setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/
1.39 espie 98: # pkg_add ${PKG_PATH}gimp-1.1.17.tgz
1.31 espie 99: </pre>
100:
101: <h3><font color=#0000e0>Managing installed packages</font></h3>
102:
1.33 espie 103: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>
1.31 espie 104: manual page holds useful information about ways to manage
105: installed packages, solve conflicts (files that already exist) and handle
106: dependencies.
107: <p>
108: As of OpenBSD 2.7, to update a package you must:
109: <ul>
1.33 espie 110: <li>Remove the old package using
111: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a>
112: <li>Add the new package using
113: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
1.31 espie 114: </ul>
115: This is slightly inconvenient, as packages may trigger dependencies, and
116: you may have to remove a large subset of packages for an update.
117:
118: <h3><font color=#0000e0>Using ports</font></h3>
119:
120: If a given package does not exist for your architecture, you may still
121: be able to compile the port. Besides, some users will want to compile
122: everything from source for various reasons.
123:
1.25 deraadt 124: <p>
1.27 brad 125: You can ftp the release version from the pub/OpenBSD/[version] (where
126: [version] is the release number) directory on any of the
127: <a href=ftp.html>ftp mirror sites</a>.
128: The release versions are the ones we ship on our CDROM, and have gone
129: through more testing than any snapshot.
1.30 espie 130: Further information is available in the
131: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">ports(7)</a> man page.
132:
133: <h3><font color=#0000e0>Ports update for an OpenBSD release</font></h3>
1.27 brad 134:
135: <p>
1.31 espie 136: The ports tree, like the rest of OpenBSD, is constantly changing.
1.30 espie 137: The normal life cycle of the ports tree is as follows:
138: <ul>
139: <li>Track the latest release of OpenBSD for a few months after the release
140: comes out.
141: <li>Switch to tracking OpenBSD-current about two months before the next
142: release.
143: </ul>
144: The change of status will be widely publicized on the
145: <a href=mail.html>Mailing lists</a>.
146:
1.37 marc 147: <p>
148: The current ports tree <strong>may not</strong> be used with the previous
149: release once the switch to tracking OpenBSD-current occurs. This is due
150: to changes, typically with the port make process, that require code
151: based upon the OpenBSD-current source tree. To get the latest version of
152: the ports tree that will work with the previous release:
153: <ul>
154: <li>Determine the cut-off date. Example, the cut-off between 2.7 and
155: 2.8 was indicated by a message to ports@openbsd.org on Aug 16, 2000.
156: <li>Check out a version of the ports tree as of the cut-off date. The
157: steps are (assuming your ports tree came from anoncvs and live in
158: /usr/ports):
159: <pre>
160: $ cd /usr/ports
161: $ cvs -q -d anoncvs@some.anon.server:/cvs up -D 08/15/00 -Pd
162: </pre>
163: Change the name of the server and cut-off date to fit your needs.
164: </ul>
1.38 marc 165: <p>
166: The ports that build with the 2.7 release have also been put into a
167: branch of their own. Instead of grabbing the ports by date you can:
168: <pre>
169: $ cd /usr/ports
170: $ cvs -q -d anoncvs@some.anon.server:/cvs up -r OPENBSD_2_7 -Pd
171: </pre>
172: The OPENBSD_2_7 tag does not imply these ports are in any way `stable', only
173: that the ports will build on a 2.7 system. Security fixes may be added
174: to this branch.
1.30 espie 175: <p>The ports tree works as a single entity. Updating a single directory is
176: not guaranteed to work, as package dependencies may force you to update
177: and recompile vast portions of the ports tree.
1.31 espie 178: It is strongly suggested that people don't track ports-current unless
1.30 espie 179: they're prepared to deal with various problems.
1.33 espie 180: <a href=mail.html>Mailing lists</a> such as
181: <code>source-changes@openbsd.org</code> or
182: <code>tech@openbsd.org</code> will probably be invaluable.
1.27 brad 183:
184: <p>
1.29 espie 185: The ports-current tree can be retrieved via:
1.25 deraadt 186: <ul>
187: <li><a href=anoncvs.html>Anonymous CVS</a> (see link). The command is
188: essentially <strong>cvs get ports</strong>.
189: <li>Anonymous ftp from
190: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">
191: ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz</a>.
1.19 marc 192: This archive is updated nightly.
1.32 naddy 193: <li><a href="cvsup.html">CVSup</a>. See the example for using CVSup in
194: <a href="cvsup.html#checkout">checkout mode</a>.
1.25 deraadt 195: <li>Your web browser using the
196: <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">CVS
1.20 marc 197: web interface</a>.
1.25 deraadt 198: </ul>
199:
1.35 espie 200: <h3><font color=#0000e0>Ports and XFree</font></h3>
201: There is some special magic in the OpenBSD XFree configuration files
202: that allows the ports tree to install imake-based applications under
203: /usr/local.
204:
205: <p>OpenBSD currently does not ship with XFree 4.0.x for various reasons.
206: This ports magic does not work with the XFree 4.0.x distribution.
207: You will need to apply the patch in
208: <code>/usr/ports/infrastructure/patches/patch-xfree-4.0</code>
209: to a default binary XFree 4.0.x distribution for it to work with the OpenBSD
210: ports tree.
211:
1.25 deraadt 212: <h3><font color=#0000e0>Example use of the Ports tree</font></h3>
213:
214: <p>
215: Let's say you managed to get a ports tree and you want to compile and
1.33 espie 216: install the archiving utility <strong>unzip</strong>. You should be able to
1.23 espie 217: do something like this:
1.31 espie 218:
1.11 deraadt 219: <pre>
1.31 espie 220: % cd /usr/ports/archivers/unzip
221: % su
222: # make
223: # make install
224: # exit
1.11 deraadt 225: </pre>
1.25 deraadt 226:
1.31 espie 227: Easy, huh ? Especially considering all that happened in the background:
228: <ul>
229: <li>Fetch unzip sources from an ftp site,
230: <li>Check the source archive integrity,
231: <li>Extract the unzip source,
232: <li>Apply OpenBSD specific patches,
233: <li>Configure and build the program,
234: <li>Create a binary package under /usr/ports/packages,
235: <li>Install that package.
236: </ul>
1.25 deraadt 237:
238: <p>
1.31 espie 239: In OpenBSD 2.7, a large proportion of the ports automatically build
240: packages when installing.
241: In OpenBSD current, almost all ports follow that standard.
242:
243: <p>
244: As ports get built, the /usr/ports/distfiles directory gets filled with
245: program sources, and /usr/ports/packages gets filled with binary packages.
246: Users with low connectivity may refer to mirror-distfiles(7) for
247: an efficient way to grab all distfiles at once.
248: Note that the OpenBSD CD only include the ports tree and selected packages.
249: If you wish to have the distfiles, you will have to get them through an
250: independent way.
1.25 deraadt 251:
252: <h3><font color=#0000e0>Creating new ports</font></h3>
253: <p>
254: If you are interested in helping to expand the OpenBSD ports tree
255: you should first read <a href="porting.html">porting.html</a>.
256: That page references the porting section of the
257: <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
258: as well as OpenBSD specific policies and hints.
259:
260: <h3><font color=#0000e0>Problems and contacts</font></h3>
261:
262: <p>
1.31 espie 263: If you have trouble with existing ports, or need information about creating new ports,
264: please send e-mail to the OpenBSD
1.27 brad 265: ports mailing list, <a href="mailto:ports@openbsd.org">ports@openbsd.org</a>.
1.25 deraadt 266: Corrections are always welcome, but in any case do please provide:
267: <ul>
268: <li>The output of <code>uname -a</code>,
269: <li>Your OpenBSD version, including any patches you may have applied,
270: <li>A complete description of the problem.
271:
272: </ul>
273:
274: <hr>
275: <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
276: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.44 ! espie 277: <br><small>$OpenBSD: ports.html,v 1.43 2000/11/23 19:06:20 jufi Exp $</small>
1.25 deraadt 278: </body>
1.11 deraadt 279: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to ports.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www