Annotation of www/checklist.html, Revision 1.34
1.14 rohee 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
1.1 marc 2: <html>
1.20 turan 3: <head>
4: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5: <meta name="resource-type" content="document">
6: <meta name="description" CONTENT="How to make/update an OpenBSD port.">
7: <meta name="keywords" content="openbsd,ports">
8: <meta name="distribution" content="global">
1.22 rohee 9: <meta name="copyright" content="This document copyright 1998-2000 by OpenBSD.">
1.20 turan 10:
11: <title>OpenBSD Porting Checklist</title>
1.1 marc 12: </head>
1.20 turan 13:
1.22 rohee 14: <body text=Black bgcolor=White link="#23238E">
1.20 turan 15: <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >
16:
17: <h2><font color="#e00000">OpenBSD Porting Checklist</font></h2>
18:
19: This document describes how to make or upgrade a port. It is a useful
1.33 pvalchev 20: reminder of things to do. This is neither totally accurate nor perfect.
1.28 espie 21: Direct comments and questions to <a href="mailto:ports@openbsd.org">
22: ports@openbsd.org </a>.
1.20 turan 23:
24: <hr>
25: <ol>
26:
1.22 rohee 27: <li>
1.20 turan 28: If you want to be a maintainer, subscribe to
29: <a href="mailto:ports@openbsd.org"> ports@openbsd.org.</a>
30: <ul><li>
31: This is where all ports discussions take place.
32: <li>
33: Reading this list is important since many announcements go over this list.
34: <li>
1.33 pvalchev 35: You will find a lot of porting-savvy people there. They can often give you
1.20 turan 36: good advice or test ports for you.
37: </ul>
38:
1.22 rohee 39: <br><li>
1.29 espie 40: Being a maintainer means <strong>more</strong> than just submitting ports.
41: It also means trying to keep them up-to-date, and to answer questions about
42: them.
43:
44: <br><li>
1.20 turan 45: Check out a copy of the ports tree from cvs.
1.33 pvalchev 46: You can find instructions on how to do this at
1.20 turan 47: <a href="http://www.openbsd.org/anoncvs.html">
48: http://www.openbsd.org/anoncvs.html</a>.
49:
1.22 rohee 50: <br><br><li>
1.20 turan 51: Pick a place to put your port and create the basic
52: infrastructure there. Use the template Makefile at
53: <code>/usr/ports/infrastructure/templates/Makefile.template</code>.
1.25 reinhard 54:
55: <br>
56: NEED_VERSION relates to the version in the $OpenBSD tag of
57: <tt>$(PORTSDIR)/infrastructure/mk/bsd.port.mk</tt>: e.g.
58: <tt>$OpenBSD: bsd.port.mk,v 1.287 ...</tt> would get
59: <tt>NEED_VERSION=1.287</tt> in your Makefile.
1.30 espie 60: The fool-proof and right way is to choose the most recent version you can
1.25 reinhard 61: find. As you are a port developer, you are supposed to update
62: your ports, including bsd.port.mk.
63: <br>
64:
1.20 turan 65: <ul><li>
66: Create the directories <code>files, patches, pkg</code>.
67: <li>
1.31 reinhard 68: Create these empty files <code>pkg/DESCR, pkg/PLIST</code>
1.20 turan 69: </ul>
70:
1.22 rohee 71: <br><li>
1.20 turan 72: Add the fetch portions of the Makefile.
73: <ul><li>
1.27 naddy 74: Fill in EXTRACT_SUFX if its anything besides .tar.gz. Other examples are
1.20 turan 75: .tar.Z, or .tgz.
76: <li>
77: Fill in DISTNAME which is the name of the file minus the extract suffix. E.g. if you have foo-1.0.tar.gz, DISTNAME is foo-1.0.
78: <li>
79: Fill in MASTER_SITES which is a URL to the directory where the distfile
1.22 rohee 80: is kept. E.g. ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/ . <strong>Don't forget
81: the trailing slash.</strong> Try to have at least three distinct sites as well.
1.20 turan 82: Place the most easily accessible first as they are traversed in order.
83: <li>
84: Keep in mind that fetch references the file as
1.32 naddy 85: ${MASTER_SITES}${DISTNAME}${EXTRACT_SUFX}. All three are used. Don't
1.20 turan 86: set DISTNAME to point to the file directly.
87: <li>
1.33 pvalchev 88: You can check to see if you have filled these values in correctly by typing
1.20 turan 89: <b>make fetch-all</b>
90: </ul>
91: <p>
92: For more complex ports, you have more options and tools available to you:
93: <ul><li>
94: You also have the variable PATCHFILES available. This is a list of vendor
1.22 rohee 95: (not OpenBSD) patches to the port. Common uses are things like security
1.20 turan 96: or reliability fixes.
97: <li>
98: If your ports are available over large public mirrors such as GNU, SunSite, or
99: CPAN, we have already provided a list of sites for your use in
100: /usr/ports/infrastructure/template/network.conf.template.
101: Set MASTER_SITES to ${MASTER_SITE_GNU}, or ${MASTER_SITE_SUNSITE}, etc.
102: To simplify this process, the construct %SUBDIR% is replaced by the variable
103: MASTER_SITE_SUBDIR in your Makefile.
104: <li>
105: Ports normally correspond to given versions of software. Once they are retrieved, files are checksummed and compared to the recorded
106: checksum in files/md5. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers:
107: don't retrieve foo-latest.tar.gz if it is a link to foo-1.0.5.tar.gz. If necessary, gently ask the original program author
108: to make such distinctions clear.
109: <li>
110: If a given port needs more than about 5 DISTFILES + PATCHFILES to work, use DIST_SUBDIR to avoid cluttering
111: /usr/ports/distfiles too much.
112: <li>
113: DIST_SUBDIR must not include version numbers. When the port is updated to a later version, some distfiles may not change, but will be
114: refetched if DIST_SUBDIR is changed. Even if all distfiles change, it is easier for the user to track cruft.
115: <li>
116: All DISTFILES and PATCHFILES don't necessarily come from the same set of MASTER_SITES. Supplementary sites can be
117: defined using the variables MASTER_SITES0 to MASTER_SITES9. Just write DISTFILES=foo-1.0.5.tar.gz:5 to
118: retrieve foo-1.0.5.tar.gz from MASTER_SITES5.
119: <li>
120: Some ports don't always need to retrieve all files in all circumstances. For instance, some ports may have some compilation options, and
121: associated files which are only required in such a case. Or they may need some files for some architectures only. In such a case, those
122: supplementary optional files must be mentioned in the SUPDISTFILES variable. Targets such as makesum or
123: mirror-distfiles will fetch those supplementary files that the casual user doesn't need.
124: </ul>
1.1 marc 125:
1.22 rohee 126: <br><li>
1.20 turan 127: Create a checksum in <i>files/md5</i> by typing <b>make makesum</b>.
128: Then verify the checksum is correct by typing <b>make checksum</b>
129: <ul><li>
130: In some rare cases, files checksums can't be verified reliably. By all means, porters should try to find sites that are reliable. Communicating
131: with the software author and the archive site maintainer at this stage is highly desirable. In the worst case, non-checksummable files can be
132: mentioned in the IGNOREFILES variable.
133: <li>
134: All files in DISTFILES are usually processed during make extract. EXTRACT_ONLY may be used to limit extraction to a
135: subset of files (possibly empty). The customary use of this variable is to customize extraction: for instance, if some DISTFILES need
136: some special treatment, they will be removed from EXTRACT_ONLY and handled manually at post-extract stage.
137: For historic reasons, make extract does set up the working directory first along with extracting files. Thus, providing a
138: pre-extract or a do-extract target is highly unusual (and fairly suspicious behavior, indicative of a high degree of obfuscation
139: in the port).
140: <li>
141: Patches that need specific treatment should be mentioned in DISTFILES, and removed from EXTRACT_ONLY, for historic reasons.
142: </ul>
1.1 marc 143:
1.22 rohee 144: <br><li>
1.20 turan 145: Extract the port with <b>make extract</b>. Pay attention to where the base
1.33 pvalchev 146: of the sources are. Usually, it's <i>work/DISTNAME</i>. You may need to modify
1.20 turan 147: the Makefile's WRKDIST variable if it is different.
1.9 espie 148:
1.22 rohee 149: <br><br><li>
1.20 turan 150: Read the installation documentation and note what you have to do to build
151: the port and any special options that might be needed.
1.22 rohee 152:
153: <br><br><li>
1.20 turan 154: Now is also a good time to figure out what kind of licensing restrictions
1.33 pvalchev 155: apply to your port. Many are freely redistributable but then again, quite
1.20 turan 156: a few are not. We need four questions answered to distribute ports
157: properly. These are the PERMIT_* values in the Makefile.
158: <ul><li>
159: PERMIT_PACKAGE_CDROM tells us if we can put the package on the cdrom.
160: <li>
161: PERMIT_PACKAGE_FTP tells us if we can put the package on the ftp sites.
162: <li>
163: PERMIT_DISTFILES_CDROM tells us if we can mirror the distfiles on the cdrom.
164: <li>
165: PERMIT_DISTFILES_FTP tells us if we can mirror the distfiles on the ftp sites.
166: </ul><p>
167: Set these values to Yes if it is permitted or to a comment string stating why
168: it is not. Pay attention to any special conditions you may need to fulfill
169: later on. E.g. some ports require to install a copy of the license. We
170: recommend you place the license in <code>/usr/local/share/DISTNAME/</code>.
171:
1.22 rohee 172: <br><br><li>
1.20 turan 173: Add configuration options to Makefile and/or create the configuration script.
174: <ul><li>
175: You can add a port configuration script named `configure' to a directory
176: named <code>scripts/</code>. This will be run before any configuration
177: specified by GNU_CONFIGURE or HAS_CONFIGURE is run.
178: <li>
179: If GNU_CONFIGURE is used you may want to run ./configure --help
180: to see what options are available.
181: <li>
182: Anything that you may want to override can be changed by adding the
183: --option flags to the CONFIGURE_ARGS parameter in the Makefile.
184: <li>
185: Use CONFIGURE_ARGS+= to append to the variable. CONFIGURE_ARGS= will
186: overwrite it.
187: </ul>
188:
1.22 rohee 189: <br><li>
1.20 turan 190: Try building the port with <b>make build</b>.
191: <ul><li>
192: If you're lucky, the port will go all the way through without errors.
193: <li>
194: If it exits with an error, you will need to generate patches for your port.
1.33 pvalchev 195: Figure out what needs to be changed and make a patch for it.
1.20 turan 196: <li>
197: Patches must be relative to ${WRKDIST}.
198: <li> The easiest way to reset the port and test your patches is
199: <b>make clean patch</b>. This will delete the work directory, re-extract,
200: and patch your port.
201: </ul>
202:
1.22 rohee 203: <br><li>
1.26 reinhard 204: Begin and cycle of <b>make build</b>, generate a patch (or use <b>make
205: update-patches</b>), and
1.20 turan 206: <b>make clean patch</b>.
207: <ul><li>
208: Patches go in the directory <i>patches/</i> and should be named patch-* with
209: * being something meaningful. We recommend you name your patches
1.26 reinhard 210: patch-FILENAME where FILENAME is the name of the file it is patching.
211: (<tt>make update-patches</tt> does this automatically for you.)
1.20 turan 212: <li>
213: Applying PATCHFILES is the first half of the make patch stage. It can be
214: invoked separately as make distpatch, which is a convenient target for
215: porters. Ignore this if you haven't set it.
216: <li>
217: Only patch one source file per patchfile, please,
218: <li>
219: Use <b>diff -p -u</b> to generate patches,
220: <li>
221: All patches MUST be relative to ${WRKDIST},
222: <li>
223: Check that patches <strong>DON'T</strong> contain tags that cvs
224: will replace. If they do, your patches won't apply after you check
225: them in. You can check in your changes with -kk to avoid this.
226: <li>
227: Add a small explanation of the patch role in the patchfile before
228: the patch itself, and an OpenBSD CVS tag <code>$OpenBSD$</code>.
229: <li>
230: <b>Please</b> feed your patches back to the author of that piece of software.
231: </ul>
232:
1.22 rohee 233: <br><li>
1.20 turan 234: Try setting <code>SEPARATE_BUILD</code><br>
235: <ul><li>
236: If the port can build with object files outside its source tree,
237: this is cleaner (many programs using <code>GNU_CONFIGURE</code> can),
238: and may help people who mount their ports tree on several arches.
239: <li>
240: This can also spare you some effort, as you will possibly be able to
241: restart the cycle at <code>configure</code> most of the time.
242: </ul>
243:
1.22 rohee 244: <br><li>
1.20 turan 245: Peruse the output (if any) and tweak any options in the Makefile.
246: To repeat issue the command `<b>make clean configure</b>'.
247: <p>
248: Note: make sure host dependent files go in <i>/etc</i> or
1.22 rohee 249: <i>/etc/<name></i>, but <strong>NEVER REPLACE OR MODIFY</strong> existing files
1.20 turan 250: in <i>/etc</i>. Best to have install place
251: in <i>/usr/local/share/<name></i> and then copy to
252: <i>/etc</i> or <i>/etc/<name></i> only if the files do not exist.
253: If the files exist, display a message that says such-and-such files need
254: to be modified. This also guarantees that the files will be included in
255: the package since everything under <i>/usr/local</i> is included in the PLIST
256:
257: <p>
258: The OpenBSD file locations are:
259: <pre>
1.1 marc 260: user executables: /usr/local/bin
261: system admin executables: /usr/local/sbin
262: program executables: /usr/local/libexec
263: libraries /usr/local/lib
1.14 rohee 264: architecture dependent data /usr/local/lib/<name>
1.1 marc 265: installed include files: /usr/local/include or
1.14 rohee 266: /usr/local/include/<name>
267: single-machine data: /etc or /etc/<name>
1.1 marc 268: local state: /var/run
269: GNU info files: /usr/local/info
270: man pages: /usr/local/man/...
1.14 rohee 271: read-only architecture-independent: /usr/local/share/<name>
272: misc documentation: /usr/local/share/doc/<name>
1.20 turan 273: </pre>
1.9 espie 274:
1.22 rohee 275: <li>
1.20 turan 276: Begin a cycle of makes until the port is ready. Patch (see above)
277: clean, and make until the port is generated. Get rid of all warnings
278: if possible, especially security related warnings.
1.22 rohee 279:
280: <br><br><li>
1.20 turan 281: Control SEPARATE_BUILD semantics.
282: You have to do this only if the port builds with
283: SEPARATE_BUILD defined.
284: Ideally, the port should no longer modify any file in
285: ${WRKSRC} after <b>make patch</b>.
286: You can check this by making sure you don't have any write access
287: to ${WRKSRC}. Then you can set
288: SEPARATE_BUILD=concurrent: someone can use the same
289: source tree to build on distinct arches simultaneously.
290: Otherwise, set <code>SEPARATE_BUILD=simple</code>: building on
291: distinct arches simultaneously may meet with problems, as some
292: source files may be regenerated at awkward moments.
1.9 espie 293:
1.22 rohee 294: <br><br><li>
1.31 reinhard 295: Add <i>COMMENT</i> in Makefile.
1.20 turan 296: COMMENT is a <strong>SHORT</strong> one-line description of the port
1.24 espie 297: (max. 60 characters). Do <strong>NOT</strong> include the package
298: name (or version number of the software) in the comment.
299: Do <strong>NOT</strong> start with an uppercase letter
300: unless semantically significant,
301: do <strong>NOT</strong> end with a period.
302: <strong>DON'T EVER START WITH AN UNDETERMINATE ARTICLE SUCH AS `a' or `as',
303: remove the article altogether.</strong>
1.31 reinhard 304:
305: <br><br><li>
306: Edit <i>pkg/DESCR</i>, <i>pkg/PLIST</i>.
307: <ul>
1.20 turan 308: <li>
309: DESCR is a longer description of the port. One to a few paragraphs
310: concisely explaining what the port does is sufficient.
311: <li>
312: PLIST is kept empty at this point.
313: </ul>
314:
1.22 rohee 315: <br><li>
1.20 turan 316: Install the application with <b>make install</b>
317: <p>
318: If the port installs dynamic libraries, check their symbol tables
319: with <code>nm</code>, as some mistaken software strips dynamic libraries,
1.34 ! jsyn 320: which may lead to weird failures later. On the other hand, executable binaries
! 321: SHOULD be stripped; <code>file</code> can be used to determine this. If the
! 322: port already contains code for stripping binaries, use it (i.e., an
! 323: 'install-strip' target); otherwise, add a provision in the port Makefile.
1.20 turan 324:
1.22 rohee 325: <br><br><li>
1.20 turan 326: <strong>Check port for security holes again</strong>. This is
327: especially important for network and setuid programs. See
328: <a href="porting.html#security">our security recommendations</a>
329: for that. Log interesting stuff and fixes in the
330: <code>pkg/SECURITY</code> file. This file
331: should list audited potential problems, along with relevant patches,
332: so that another person can see at first glance what has been done.
333: Example:
1.14 rohee 334: <pre>
335: $OpenBSD$
1.9 espie 336:
337: ${WRKDIR}/receiver.c
338: call to mktemp (wrapper function do_mktemp) does seem to be correct.
339:
340: The server makes extensive use of strlcpy/strlcat/snprintf.
1.20 turan 341: </pre>
342:
1.22 rohee 343: <li>
1.20 turan 344: Create pkg/PLIST. After the install is complete use the developer's command,
1.33 pvalchev 345: <b>make plist</b> which makes the file PLIST in the <i>pkg</i> directory.
1.20 turan 346: This file is a candidate packing list.
347: <p>
348: Beware! The files are found by timestamp. This means it does NOT:
349: <ul>
350: <li>
351: list any files installed with `tar' as their timestamp
352: will not change and thus won't be found by `find'
353: <li>
354: Update the <code>info/dir</code> file if .info files are added.
355: Also, be sure that the <code>info/dir</code> is not part of the PLIST.
356: <li>
357: Try to do anything special with links or symbolic links. A
358: cursory test of tar shows it does the right thing with links
359: and symbolic links so I don't see why we need to special case
360: anything in the packing list. But still...
361: </ul>
362: <p>
1.33 pvalchev 363: Peruse `PLIST' and verify that everything was installed and
1.20 turan 364: that it was installed in the proper locations. Anything not installed
365: can be added to a port Makefile `post-install' rule.
366:
367: <p>
1.33 pvalchev 368: Ports that install shared libraries will have another file called PFRAG.shared.
1.20 turan 369: <ul>
370: <li>
1.33 pvalchev 371: PLIST describes the files being independent of whether the architecture supports shared libraries or not.
372: <li>
373: PFRAG.shared describes only the files being additionally installed on those architectures that support
1.20 turan 374: shared libraries.
375: <li>
1.33 pvalchev 376: PFRAG.noshared describes only the files being additionally installed on architectures that do not
377: support shared libraries.
1.20 turan 378: </ul>
379:
1.22 rohee 380: <br><li>
1.20 turan 381: Keep repeating uninstall and reinstall until perfect.<br>
382: <em>Perfect</em> is when everything installs and uninstalls
383: in its proper location. `pkg_delete <pkg_name>' is
384: used to uninstall. `sudo make reinstall' is used to reinstall. See the
385: `pkg_create' man page for other commands that may be added
386: to PLIST to ensure all is cleaned up. After an uninstall the command
1.33 pvalchev 387: <p><code>find /usr/local -newer work/fake-${MACHINE_ARCH}[-${FLAVOR}]/.install_started -print</code>
1.20 turan 388: <p>should only list standard directory names.
389:
1.22 rohee 390: <br><br><li>
1.20 turan 391: Test the packaging:<br>
392: After the port installs correctly issue the command
393: <code>make package</code> to create a package. To test the
394: package first do a <code>pkg_delete</code> and then do a
395: <code>pkg_add</code> The results after an add should EXACTLY
396: match the results after a `make install'.
1.9 espie 397:
1.22 rohee 398: <br><br><li>
1.20 turan 399: Mail <a href="mailto:ports@openbsd.org">ports@openbsd.org</a> with a short
400: note asking for comments and testing. Attach the port to this email and
1.30 espie 401: sent it out.
1.20 turan 402: <p>
403: Try to get others to test it on a variety of platforms for you.
404: <ul><li>
405: The DEC Alpha is good because it has only static libraries and because
1.22 rohee 406: <code>sizeof(int) != sizeof(long)</code>
1.20 turan 407: <li>
408: Sun SPARC is good because it is very common and because its byte order is
409: the reverse of i386; if you developed on SPARC, of course, you'd want it
410: tested on i386).
411: </ul>
412:
1.22 rohee 413: <br><li>
1.20 turan 414: Incorporate any feedback you get. Test it again on your platform.
415: Get those who gave you feedback to test it again from your new port.
416:
1.22 rohee 417: <br><br><li>
1.20 turan 418: Finally, include it in the "ports" tree.
419: <p>
420: If you do not have CVS access, ask someone on
1.30 espie 421: <a href="mailto:ports@openbsd.org">ports@openbsd.org</a> to commit it.
1.9 espie 422:
1.22 rohee 423: <br><br><li>
1.20 turan 424: If you are a developer with CVS access, check it in.
425: We normally use "import" for a new port,
426: rather than adding a zillion (or a dozen) files individually.
427: Import uses "vendor branch" version numbers like 1.1.1.1, but don't worry
428: about that! :-) If you make changes to a specific file (edit, then
429: cvs commit), it will be 1.2, and that will be used.
430: <p>
431: In short, import is typically used when a port is created.
432: From that point on cvs add and cvs rm are typically used to add or remove
433: files, and the normal edit->commit cycle for changes.
434: You might use something like this:
435: <pre>
1.4 ian 436: cd kaffe1
437: make clean # you really really don't want to check in all of work!
438: cvs -d cvs.openbsd.org:/cvs import -m 'kaffe port' ports/lang/kaffe1 \
439: <I>YourName</I> <I>YourName_YYYY-MMM-DD</I>
1.20 turan 440: </pre>
441: <ul><li>
442: -d cvs.openbsd.org:/cvs says where cvs lives. This can be omitted if you
1.21 form 443: have a CVSROOT environment variable defined.
1.20 turan 444: <li>
445: -m 'kaffe port' is your login message. Change it to whatever you like
446: <li>
447: ports/lang/kaffe1 is the path relative to /cvs where the port lives
448: <li>
449: <i>YourName</i> (replaced with your login name) is the "vendor tag".
450: You imported it so you are the vendor.
451: <li>
452: <i>YourName_YYYY-MMM-DD</i> (e.g., ian_2000-Jan-01)
453: is the 'vendor release tag'. This is as good as any.
454: </ul>
455: As a real example, here is the output of checking in the Kaffe1 port,
456: which one of us did on September 8, 1998:
457: <pre>
1.4 ian 458: $ cd kaffe1
459: $ make clean >/dev/null
460: $ cvs import -m 'kaffe1.0(==JDK1.1) port' ports/lang/kaffe1 ian ian_1998-Sep-08
461: ian@cvs.openbsd.org's password: (not shown, obviously)
462: I ports/lang/kaffe1/CVS
463: I ports/lang/kaffe1/files/CVS
464: I ports/lang/kaffe1/pkg/CVS
465: N ports/lang/kaffe1/Makefile
466: cvs server: Importing /cvs/ports/lang/kaffe1/files
467: N ports/lang/kaffe1/files/md5
468: cvs server: Importing /cvs/ports/lang/kaffe1/pkg
469: N ports/lang/kaffe1/pkg/COMMENT
470: N ports/lang/kaffe1/pkg/DESCR
471: N ports/lang/kaffe1/pkg/PLIST
472:
473: No conflicts created by this import
474: $
1.20 turan 475: </pre>
476:
1.22 rohee 477: <li>
1.20 turan 478: Last but not least, add a one-line entry for the new port
479: in its parent directory's makefile, i.e., for ports/lang/kaffe1,
480: add it to ports/lang/Makefile.
481:
1.22 rohee 482: <br><br><li>
1.20 turan 483: Maintain the port! As time goes by, problems may arise, or new versions
484: of the software may be released. You should strive to keep your port up
1.22 rohee 485: to date. In other words - iterate, test, test, iterate...
1.29 espie 486:
487: <br><li>
488: When updating a port, remember to handle dependencies! You shouldn't break any
489: port that depends on yours. In case of problems, communicate with the
490: maintainers of such ports. Likewise, be alert for dependency updates, and
491: check that the maintainer did their job.
1.22 rohee 492: </ol>
1.20 turan 493:
494: Thank you for supporting the OpenBSD "ports" process!
495: <hr>
496: <a href="porting.html"><img height=24 width=24 src=back.gif
497: border=0 alt=Porting></a>
498: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.34 ! jsyn 499: <br><small>$OpenBSD: checklist.html,v 1.33 2001/07/05 18:52:09 pvalchev Exp $</small>
1.20 turan 500: </body>
1.1 marc 501: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to checklist.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www