Building an OpenBSD port

=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/porting.html,v retrieving revision 1.19 retrieving revision 1.20 diff -c -r1.19 -r1.20 *** www/Attic/porting.html 1999/02/27 16:37:29 1.19 --- www/Attic/porting.html 1999/02/27 16:49:44 1.20 *************** *** 1,3 **** --- 1,4 ---- + Building an OpenBSD port

!

Building an OpenBSD port

So you've just compiled your favorite software package on your OpenBSD machine and you want to share your effort by turning --- 12,25 ---- Building an OpenBSD port

!

Building an OpenBSD port

So you've just compiled your favorite software package on your OpenBSD machine and you want to share your effort by turning *************** *** 32,42 ****

Submit the port. Create a gzipped tarball of the port directory. You can then either place it on a public FTP or HTTP server, sending ! its address to ports@openbsd.org or send the port mime encoded to the same address. Pick whichever method works best for you.

!

Available Porting Information

The file /usr/share/mk/bsd.port.mk. This is the system ports makefile included at the end of each individual --- 33,43 ----
Submit the port. Create a gzipped tarball of the port directory. You can then either place it on a public FTP or HTTP server, sending ! its address to ports@openbsd.org or send the port mime encoded to the same address. Pick whichever method works best for you.
!
Available Porting Information
- The file /usr/share/mk/bsd.port.mk. This is the system ports makefile included at the end of each individual *************** *** 54,60 ****
- The OpenBSD ports mailing list, ports@OpenBSD.ORG.
!
OpenBSD Porting Policy
- OpenBSD does NOT use /usr/local/etc/rc.d.
  /usr/local is often shared between several machines --- 55,61 ----
- The OpenBSD ports mailing list, ports@OpenBSD.ORG.
!
OpenBSD Porting Policy
- OpenBSD does NOT use /usr/local/etc/rc.d.
  /usr/local is often shared between several machines *************** *** 79,93 **** achieve this goal you must feed any OpenBSD patches back to the application maintainer.
! !
Security recommendations
There are many security problems to worry about. If you are not absolutely sure of what you are doing please request help from the ports mailing list.
- Do not use alpha or beta code when preparing a port. Use the latest regular or patch release.
- Any software to be installed as a server should be scanned --- 80,94 ---- achieve this goal you must feed any OpenBSD patches back to the application maintainer.
! !
Security recommendations
There are many security problems to worry about. If you are not absolutely sure of what you are doing please request help from the ports mailing list.
- Do not use alpha or beta code when preparing a port. Use the latest regular or patch release.
- Any software to be installed as a server should be scanned *************** *** 193,199 **** library writer point of view. Don't try to port libraries unless you understand this issue thoroughly.
!
Generic porting hints
- __OpenBSD__ should be used sparingly, if at all. Constructs that look like --- 194,200 ---- library writer point of view. Don't try to port libraries unless you understand this issue thoroughly.
!
Generic porting hints
- __OpenBSD__ should be used sparingly, if at all. Constructs that look like *************** *** 291,297 **** s = foo_gcvt(n, 15, b);
!
Other Helpful Hints
- Recent versions of bsd.port.mk set the installers path. Specifically, they set /usr/bin and --- 292,298 ---- s = foo_gcvt(n, 15, b);
!
Other Helpful Hints
- Recent versions of bsd.port.mk set the installers path. Specifically, they set /usr/bin and *************** *** 343,349 ****
! www@openbsd.org !
$OpenBSD: porting.html,v 1.19 1999/02/27 16:37:29 rohee Exp $ --- 344,350 ----

! www@openbsd.org !
$OpenBSD: porting.html,v 1.20 1999/02/27 16:49:44 rohee Exp $