Annotation of www/ports.html, Revision 1.89
1.47 naddy 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
1.11 deraadt 2: <html>
1.25 deraadt 3: <head>
1.88 nick 4: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.25 deraadt 5: <meta name="resource-type" content="document">
1.47 naddy 6: <meta name="description" content="The OpenBSD Ports and Packages Collection">
1.25 deraadt 7: <meta name="keywords" content="openbsd,ports">
8: <meta name="distribution" content="global">
1.77 nick 9: <meta name="copyright" content="copyright 1997-2004 by OpenBSD.">
1.27 brad 10: <title>OpenBSD Ports and Packages</title>
1.47 naddy 11: <link rev="made" href="mailto:www@openbsd.org">
1.43 jufi 12: </head>
1.25 deraadt 13:
14: <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
15:
1.88 nick 16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.30 espie 17:
1.88 nick 18: <h2><font color="#e00000">The Ports & Packages collection</font></h2>
1.25 deraadt 19:
1.47 naddy 20: <hr>
21:
1.88 nick 22: <h3><font color="#0000e0">Index</font></h3>
1.53 naddy 23: <ul>
1.88 nick 24: <li><a href="#Motivation">Motivation</a></li>
25: <li><a href="#Get">Getting Packages</a></li>
26: <li><a href="#stable">Ports and Packages Update for an OpenBSD Release</a></li>
27: <li><a href="#Manage">Managing Installed Packages</a></li>
28: <li><a href="#Use">Using Ports</a></li>
29: <li><a href="#Life">Life Cycle of the Ports Tree</a></li>
30: <li><a href="#X">Ports and the X Window System</a></li>
31: <li><a href="#Example">Example Use of the Ports Tree</a></li>
32: <li><a href="#Advanced">Advanced Usage of the Ports Tree</a></li>
33: <li><a href="#Create">Creating New Ports</a></li>
34: <li><a href="#Lag">When a Port Is Lagging Behind the Mainstream Version</a></li>
35: <li><a href="#Help">Problems and Contacts</a></li>
1.53 naddy 36: </ul>
37:
38: <hr>
39:
1.88 nick 40: <h3><font color="#0000e0"><a name="Motivation">Motivation</a></font></h3>
1.25 deraadt 41:
1.88 nick 42: OpenBSD is a fairly complete system of its own, but still there is a lot
43: of software that one might want to see added. However, there is the problem
44: of where to draw the line as to what to include, as well as the occasional
45: licensing and export restriction problems. As OpenBSD is supposed to be
46: a small stand-alone UNIX-like operating system, some things just can't be
47: shipped with the system.
1.25 deraadt 48:
49: <p>
1.47 naddy 50: <strong><font color="#e00000">
1.88 nick 51: The ports & packages collection does NOT go through the thorough security audit that OpenBSD follows.
52: Although we strive to keep the quality of the packages collection high, we just do not have enough human
53: resources to ensure the same level of robustness and security.
1.31 espie 54: </font></strong>
1.25 deraadt 55:
56: <p>
1.88 nick 57: The port collection, originally borrowed from
58: <a href="http://www.freebsd.org/">FreeBSD</a>, fills this gap.
59: The concept is to have, for each third-party software, a Makefile that
60: controls
1.25 deraadt 61: <ul>
1.88 nick 62: <li>where to fetch it,
63: <li>how to do the fetch,
64: <li>what it depends upon (if anything),
65: <li>how to alter the sources (if needed),
66: <li>and how to configure, build and install it.
1.25 deraadt 67: </ul>
1.88 nick 68: This information is kept in a directory hierarchy under the
69: /usr/ports directory.
1.31 espie 70:
71: <p>
1.88 nick 72: Packages are the binary equivalent of ports. A compiled port becomes
73: a package that can be registered into the system using
1.63 rohee 74: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
1.31 espie 75:
76: <p>
1.47 naddy 77: <strong><font color="#e00000">
1.88 nick 78: Packages look like simple <code>.tgz</code> bundles, but they should
79: always be added using
80: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>,
81: as there might be some extra information that only
82: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
83: knows how to handle.</font></strong>
84: Tip: you can distinguish between packages and <strong>.tgz</strong> bundles
85: using
86: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a>.
1.31 espie 87:
1.88 nick 88: <h3><font color="#0000e0"><a name="Get">Getting Packages</a></font></h3>
1.31 espie 89:
1.88 nick 90: A large collection of pre-compiled packages is available for most common
91: architectures.
1.31 espie 92: <ul>
1.88 nick 93: <li>On the CD-Rom (that you can order <a href="orders.html">here</a>),
94: <li>On the <a href=ftp.html>ftp mirror sites</a>.
95: <li>Browsed and retrieved from the web package lists:
1.40 beck 96: <ul>
1.89 ! pvalchev 97: <li><a href="http://www.openbsd.org/4.0_packages/">Packages for OpenBSD 4.0</a>
1.88 nick 98: <li><a href="http://www.openbsd.org/3.9_packages/">Packages for OpenBSD 3.9</a>
99: <li><a href="http://www.openbsd.org/3.8_packages/">Packages for OpenBSD 3.8</a>
100: <li><a href="http://www.openbsd.org/3.7_packages/">Packages for OpenBSD 3.7</a>
1.40 beck 101: </ul>
1.31 espie 102: </ul>
103:
1.44 espie 104:
1.88 nick 105: Adding a package is as easy as
106: <code>pkg_add pkgname.tgz</code>.
107: If you are grabbing packages from a single source (a package repository),
108: set PKG_PATH to that repository URL, in order to grab dependencies.
1.31 espie 109:
110: <p>
1.88 nick 111: For instance, to install the Gimp package for the 3.9 release on an i386
112: machine off the ftp site (including dependencies), do:
1.31 espie 113:
114: <pre>
1.86 steven 115: # export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/3.9/packages/i386/
116: # pkg_add gimp-2.2.10.tgz
1.31 espie 117: </pre>
118:
1.88 nick 119: <h3><font color="#0000e0"><a name="stable">Ports and Packages Update for an OpenBSD Release</a></font></h3>
1.45 espie 120: <p>
1.88 nick 121: The 2.7 release saw the introduction of a stable branch for the ports tree.
1.45 espie 122: <p>
1.88 nick 123: For instance, to grab the stable branch for the 3.9 release:
1.45 espie 124: <pre>
125: $ cd /usr/ports
1.86 steven 126: $ cvs -q -d anoncvs@some.anon.server:/cvs up -r OPENBSD_3_9 -Pd
1.45 espie 127: </pre>
128: <p>
1.88 nick 129: Starting with the 2.8 release, selected binary packages are also made
130: available.
131: Please refer to the
132: <a href="pkg-stable.html">stable packages page</a> to find out about
133: updated packages and important updates to the stable branch.
134: If you want to receive security announcements, you can subscribe
135: to the ports-security mailing list.
1.45 espie 136: </p>
137: <p>
1.88 nick 138: Package names are <strong>always</strong> changed in case of a package
139: update, to avoid any risk of confusion between a package from the release
140: and a bug-fixed package.
1.45 espie 141: </p>
142:
1.88 nick 143: <h3><font color="#0000e0"><a name="Manage">Managing Installed Packages</a></font></h3>
1.31 espie 144:
1.88 nick 145: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>
146: manual page holds useful information about ways to manage
147: installed packages, solve conflicts (files that already exist) and handle
148: dependencies.
1.31 espie 149: <p>
1.88 nick 150: As of OpenBSD 2.8, to update a package you must:
1.31 espie 151: <ul>
1.88 nick 152: <li>Remove the old package using
153: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a>
154: <li>Add the new package using
155: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
1.31 espie 156: </ul>
1.88 nick 157: This is slightly inconvenient, as packages may trigger dependencies, and
158: you may have to remove a large subset of packages for an update.
1.31 espie 159:
1.88 nick 160: <h3><font color="#0000e0"><a name="Use">Using Ports</a></font></h3>
1.31 espie 161:
1.88 nick 162: If a given package does not exist for your architecture, you may still
163: be able to compile the port. Besides, some users will want to compile
164: everything from source for various reasons.
165:
166: <p>
167: You can ftp the release version from the pub/OpenBSD/[version] (where
168: [version] is the release number) directory on any of the
169: <a href=ftp.html>ftp mirror sites</a>.
170: The release versions are the ones we ship on our CDROM, and have gone
171: through more testing than any snapshot.
172: Further information is available in the
173: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">ports(7)</a> man page.
174:
175: <h3><font color="#0000e0"><a name="Life">Life Cycle of the Ports Tree</a></font></h3>
176:
177: <p>
178: The ports tree, like the rest of OpenBSD, is constantly changing.
179: <p>
180: The current ports tree <strong>may not</strong> be used with the previous
181: release. This is due to changes, typically with the port make process,
182: that require code based upon the OpenBSD-current source tree.
183: <p>The ports tree works as a single entity. Updating a single directory is
184: not guaranteed to work, as package dependencies may force you to update
185: and recompile vast portions of the ports tree.
186: It is strongly suggested that people don't track ports-current unless
187: they're prepared to deal with various problems.
188: <a href=mail.html>Mailing lists</a> such as
189: <code>ports-changes@openbsd.org</code> or
190: <code>tech@openbsd.org</code> will probably be invaluable.
191:
192: <p>You are advised to track ports-stable on a production machine:
193: we will try to keep the stable ports tree up-to-par with respect to
194: problems, and to provide timely binary updates as well.
195:
196: <p>Note that vanishing distfiles is not an issue, as
197: ftp.openbsd.org holds the complete repository. Even changing checksums is
198: not an issue: you can issue the command
1.59 espie 199: <pre>
200: make checksum REFETCH=true
201: </pre>
1.88 nick 202: to make sure you are grabbing the correct distfile for your ports tree.
1.59 espie 203:
1.88 nick 204: For definitions of <i>current</i> and <i>stable</i>, see the
205: <a href="faq/faq5.html#Flavors">OpenBSD's flavors</a>.
1.59 espie 206:
207:
1.88 nick 208: <p>A list of <a href="portsplus/index.html">daily changes</a> to ports
209: and ports-current is available.
1.47 naddy 210:
1.27 brad 211: <p>
1.88 nick 212: The ports-current tree can be retrieved via:
1.25 deraadt 213: <ul>
1.88 nick 214: <li><a href=anoncvs.html>Anonymous CVS</a> (see link). The command is
215: essentially <strong>cvs get ports</strong>.
216: <li>Anonymous ftp from
217: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">
218: ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz</a>.
219: This archive is updated nightly.
220: <li><a href="cvsup.html">CVSup</a>. See the example for using CVSup in
221: <a href="cvsup.html#checkout">checkout mode</a>.
222: <li>Your web browser using the
223: <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">CVS
224: web interface</a>.
1.25 deraadt 225: </ul>
226:
1.88 nick 227: <h3><font color="#0000e0"><a name="X">Ports and the X Window System</a></font></h3>
228: There is some special magic in the OpenBSD X configuration files
229: that allows the ports tree to install imake-based applications under
230: /usr/local.
1.35 espie 231:
1.88 nick 232: <h3><a name="Example"></a><font color="#0000e0">Example Use of the Ports Tree</font></h3>
1.54 lebel 233:
234: <p>
1.88 nick 235: Let's say you managed to get a ports tree and you want to compile and
236: install the archiving utility <strong>unzip</strong>. You should be able to
237: do something like this:
1.31 espie 238:
1.11 deraadt 239: <pre>
1.31 espie 240: % cd /usr/ports/archivers/unzip
241: % su
242: # make
243: # make install
244: # exit
1.11 deraadt 245: </pre>
1.25 deraadt 246:
1.88 nick 247: Easy, huh ? Especially considering all that happened in the background:
1.31 espie 248: <ul>
1.88 nick 249: <li>Fetch unzip sources from an ftp site,
250: <li>Check the source archive integrity,
251: <li>Extract the unzip source,
252: <li>Apply OpenBSD specific patches,
253: <li>Configure and build the program,
254: <li>Create a binary package under /usr/ports/packages,
255: <li>Install that package.
1.31 espie 256: </ul>
1.25 deraadt 257:
258: <p>
1.88 nick 259: With OpenBSD 3.0, almost all ports automatically build
260: packages when installing.
1.31 espie 261:
262: <p>
1.88 nick 263: As ports get built, the /usr/ports/distfiles directory gets filled with
264: program sources, and /usr/ports/packages gets filled with binary packages.
265: Users with low connectivity may refer to
266: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mirroring-ports&sektion=7&format=html">mirroring-ports(7)</a> for
267: an efficient way to grab all distfiles at once. In OpenBSD-current, you
268: can use the script /usr/ports/infrastructure/fetch/clean-old to track
269: old distfiles.
270: Note that the OpenBSD CD only includes the ports tree and selected packages.
271: If you wish to have the distfiles, you will have to get them through an
272: independent way.
273:
274: <h3><font color="#0000e0"><a name="Advanced"></a>Advanced Usage of the Ports Tree</font></h3>
275:
276: <p>
277: Ports tree has many features for the advanced user that make it a valuable
278: tool beyond basic installation. Advanced users may wish to tamper with
279: the makefiles (you should read the
1.63 rohee 280: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=make&sektion=1&format=html">make(1)</a>
1.88 nick 281: manual page first) or set various variables from the make command-line or in
282: <tt>/etc/mk.conf</tt>. These variables are described in detail in the
1.63 rohee 283: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bsd.port.mk&sektion=5&format=html">bsd.port.mk(5)</a>
1.88 nick 284: manual page, and the porting documents below.
1.55 heko 285: </p>
286:
1.88 nick 287: <h3><font color="#0000e0"><a name="Create">Creating New Ports</a></font></h3>
1.25 deraadt 288: <p>
1.88 nick 289: If you are interested in helping to expand the OpenBSD ports tree
290: you should first read <a href="porting.html">porting.html</a>.
291: That page references the
1.66 jufi 292: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html">
293: FreeBSD Porter's Handbook</a>
1.88 nick 294: as well as OpenBSD specific policies and hints.
1.56 heko 295:
1.88 nick 296: <h3><font color="#0000e0"><a name="Lag">When a Port Is Lagging Behind the Mainstream Version</a></font></h3>
1.56 heko 297:
298: <p>
1.88 nick 299: The ports collection is a volunteer project. Sometimes the project simply
300: doesn't have the developer resources to keep everything up-to-date.
301: Developers pretty much pick up what they consider interesting and can
302: test in their environment. Your <a href="goals.html#funding">donations</a>
303: count for what platforms the ports can be tested on.
1.56 heko 304: </p>
305:
306: <p>
1.88 nick 307: Some individual ports may lag behind the mainstream versions because of this.
308: The ports collection may have a version back of a program from January while a new
309: version of the program has been released by its developers in May three months ago.
310: Often this is a conscious decision; the new version may have problems in it on
311: OpenBSD that the maintainer is trying to solve, or that have simply made the
312: application worse than the old version: OpenBSD may have different
313: <a href="goals.html">goals</a> than the mainstream developers in other projects,
314: which sometimes results in features and design or implementation choices
315: that are undesirable from OpenBSD developers' point of view. The update may also be
316: postponed because the new version is not considered a crucial update.
1.56 heko 317: </p>
318:
319: <p>
1.88 nick 320: If you really need a new version of a port, you should ask the <tt>MAINTAINER</tt>
321: of the port to update the port (see <a href="#Help">below</a> on how to find out who
322: the maintainer is); if you can send patches for this, all the better. To create proper
323: patches, you should refer to the <a href="porting.html">documentation on building
324: ports</a>.
1.56 heko 325: </p>
1.25 deraadt 326:
1.88 nick 327: <h3><font color="#0000e0"><a name="Help">Problems and Contacts</a></font></h3>
1.25 deraadt 328:
329: <p>
1.88 nick 330: If you have trouble with an existing port, please send e-mail to the
331: port maintainer. To see who is the maintainer of the port, type, for
332: example:
1.54 lebel 333: <pre>
334: % cd /usr/ports/archivers/unzip
1.74 xsa 335: % make show=MAINTAINER
1.54 lebel 336: </pre>
1.88 nick 337: Alternatively, if there is no maintainer, or you can't reach
338: him/her, send mail to the OpenBSD
339: ports mailing list, <a href="mailto:ports@openbsd.org">ports@openbsd.org</a>.
340: Please don't use the misc@openbsd.org mailing list for questions about ports.
341: Corrections are always welcome, but in any case do please provide:
1.25 deraadt 342: <ul>
1.88 nick 343: <li>The output of <code>uname -a</code>,
344: <li>Your OpenBSD version, including any patches you may have applied,
345: <li>A complete description of the problem.
1.45 espie 346: </ul>
1.88 nick 347: For ports that don't build correctly, a complete build transcript is almost
348: always required. You can use the portslogger script, found in
349: /usr/ports/infrastructure/build, for this. A sample run of portslogger
350: might be:
1.54 lebel 351:
352: <pre>
353: % cd /usr/ports/archivers/unzip
354: % su
355: # mkdir -p ~/portslogs
1.63 rohee 356: # make clean install 2>&1 | /usr/ports/infrastructure/build/portslogger \
1.54 lebel 357: ~/portslogs
358: </pre>
359:
1.88 nick 360: After this, you should have a logfile of the build in your ~/portslogs directory
361: that you can send to the port maintainer. Also, make sure you are not using
362: any special options in your build, for example in /etc/mk.conf.
1.54 lebel 363:
364: <p>
1.88 nick 365: Alternatively, you can
1.45 espie 366: <ul>
1.88 nick 367: <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.
368: <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.
369: <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
370: the gcc mailing-list. It does save time if you follow their direction, and
371: provide at least the various files produced by <tt>gcc -save-temps</tt>.
1.25 deraadt 372: </ul>
373:
374: <hr>
1.88 nick 375: <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.47 naddy 376: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.89 ! pvalchev 377: <br><small>$OpenBSD: ports.html,v 1.88 2006/05/03 00:21:26 nick Exp $</small>
1.25 deraadt 378: </body>
1.11 deraadt 379: </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