=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v retrieving revision 1.53 retrieving revision 1.54 diff -c -r1.53 -r1.54 *** www/Attic/ports.html 2001/07/27 23:42:52 1.53 --- www/Attic/ports.html 2001/08/06 21:57:18 1.54 *************** *** 228,233 **** --- 228,237 ----

Example Use of the Ports Tree

+ First, please read the

/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: *************** *** 277,285 ****

Problems and Contacts

! If you have trouble with existing ports, or need information about creating new ports, ! please send e-mail to the OpenBSD ports mailing list, ports@openbsd.org. Corrections are always welcome, but in any case do please provide:

The output of uname -a, --- 281,297 ----
Problems and Contacts

! If you have trouble with an existing port, please send e-mail to the ! port maintainer. To see who is the maintainer of the port, type, for ! example: !
```
!        % cd /usr/ports/archivers/unzip
!        % make show VARNAME=MAINTAINER
! 
```
! Alternatively, if there is no maintainer, or you can't reach ! him/her, send mail to the OpenBSD ports mailing list, ports@openbsd.org. + Please don't use the misc@openbsd.org mailing list for questions about ports. Corrections are always welcome, but in any case do please provide:
- The output of uname -a, *************** *** 287,294 ****
- A complete description of the problem.
For ports that don't build correctly, a complete build transcript is almost ! always required. Some ports may have configuration issues linked to what ! is already on your machine.
- Use script(1) to create a complete build transcript. Don't remove the configure information.
- Attach the output of pkg_info(1) if it seems even remotely relevant. --- 299,322 ----
- A complete description of the problem.
For ports that don't build correctly, a complete build transcript is almost ! always required. You can use the portslogger script, found in ! /usr/ports/infrastructure/build, for this. A sample run of portslogger ! might be: ! !
```
!        % cd /usr/ports/archivers/unzip
!        % su
!        # mkdir -p ~/portslogs
!        # make clean install 2>&1 | /usr/ports/infrastructure/build/portslogger \
!                ~/portslogs
! 
```
! ! After this, you should have a logfile of the build in your ~/portslogs directory ! that you can send to the port maintainer. Also, make sure you are not using ! any special options in your build, for example in /etc/mk.conf. ! !
! Alternatively, you can
- Use script(1) to create a complete build transcript. Don't remove the configure information.
- Attach the output of pkg_info(1) if it seems even remotely relevant. *************** *** 300,305 ****
  www@openbsd.org !
  $OpenBSD: ports.html,v 1.53 2001/07/27 23:42:52 naddy Exp $ --- 328,333 ----
  www@openbsd.org !
  $OpenBSD: ports.html,v 1.54 2001/08/06 21:57:18 lebel Exp $