Packages are the binary equivalent of ports. A compiled port becomes ! a package that can be registered into the system using ! pkg_add(1)
***************
*** 184,190 ****
The current ports tree may not be used with the previous
release once the switch to tracking OpenBSD-current occurs. This is due
to changes, typically with the port make process, that require code
! based upon the OpenBSD-current source tree.
The ports tree works as a single entity. Updating a single directory is
not guaranteed to work, as package dependencies may force you to update
and recompile vast portions of the ports tree.
--- 187,194 ----
The current ports tree may not be used with the previous
release once the switch to tracking OpenBSD-current occurs. This is due
to changes, typically with the port make process, that require code
! based upon the OpenBSD-current source tree. This switch will be announced
! on the ports@openbsd.org mailing list.
The ports tree works as a single entity. Updating a single directory is
not guaranteed to work, as package dependencies may force you to update
and recompile vast portions of the ports tree.
***************
*** 225,237 ****
to a default binary XFree86 4.0.x distribution for it to work with the OpenBSD
ports tree.
!
- First, please read the Example Use of the Ports Tree
/usr/ports/README
file on your system.
-
Let's say you managed to get a ports tree and you want to compile and install the archiving utility unzip. You should be able to do something like this: --- 229,237 ---- to a default binary XFree86 4.0.x distribution for it to work with the OpenBSD ports tree. !
Example Use of the Ports Tree
Let's say you managed to get a ports tree and you want to compile and install the archiving utility unzip. You should be able to do something like this: *************** *** 262,268 ****
As ports get built, the /usr/ports/distfiles directory gets filled with program sources, and /usr/ports/packages gets filled with binary packages. ! Users with low connectivity may refer to mirror-distfiles(7) for an efficient way to grab all distfiles at once. In OpenBSD-current, you can use the script /usr/ports/infrastructure/fetch/clean-old to track old distfiles. --- 262,269 ----
As ports get built, the /usr/ports/distfiles directory gets filled with program sources, and /usr/ports/packages gets filled with binary packages. ! Users with low connectivity may refer to ! mirroring-ports(7) for an efficient way to grab all distfiles at once. In OpenBSD-current, you can use the script /usr/ports/infrastructure/fetch/clean-old to track old distfiles. *************** *** 270,275 **** --- 271,289 ---- If you wish to have the distfiles, you will have to get them through an independent way. +
Advanced Usage of the Ports Tree
+ ++ Ports tree has many features for the advanced user that make it a valuable + tool beyond basic installation. Advanced users may wish to tamper with + the makefiles (you should read the + make(1) + manual page first) or set various variables from the make commandline or in + /etc/mk.conf. These variables are described in detail in the + bsd.port.mk(5) + manual page, and the porting documents below. +
+Creating New Ports
If you are interested in helping to expand the OpenBSD ports tree *************** *** 328,333 ****
www@openbsd.org
! $OpenBSD: ports.html,v 1.54 2001/08/06 21:57:18 lebel Exp $