From trish@listmistress.dynip.com  Tue Jan 22 13:37:50 2002
Return-Path: <trish@listmistress.dynip.com>
Received: from femme.sapphite.org (bgp01560710bgs.gambrl01.md.comcast.net [68.50.32.183])
	by hub.freebsd.org (Postfix) with ESMTP id 6C0FB37B416
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 22 Jan 2002 13:37:48 -0800 (PST)
Received: from femme.sapphite.org (smmsp@localhost [127.0.0.1])
	by femme.sapphite.org (8.12.1/8.12.1) with ESMTP id g0MLbfdT000465
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 22 Jan 2002 16:37:42 -0500 (EST)
Received: (from root@localhost)
	by femme.sapphite.org (8.12.1/8.12.1/Submit) id g0MLbeaa000464;
	Tue, 22 Jan 2002 16:37:40 -0500 (EST)
Message-Id: <200201222137.g0MLbeaa000464@femme.sapphite.org>
Date: Tue, 22 Jan 2002 16:37:40 -0500 (EST)
From: Trish Lynch <trish@bsdunix.net>
Reply-To: Trish Lynch <trish@bsdunix.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Update port: security/srp, various patches and fixes for compilation
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         34183
>Category:       ports
>Synopsis:       Update port: security/srp, various patches and fixes for compilation
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    nectar
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 22 13:40:01 PST 2002
>Closed-Date:    Tue Jan 22 14:40:43 PST 2002
>Last-Modified:  Tue Jan 22 17:50:01 PST 2002
>Originator:     Trish Lynch <trish@bsdunix.net>
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
Ecartis Core
>Environment:
System: FreeBSD femme.sapphite.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Mon Dec 17 18:06:39 EST 2001 trish@femme.
sapphite.org:/admins/obj/usr/src/sys/FEMME i386


>Description:
        srp port broken, compilation breaks in several areas, resulting in port not building
  specifically in base/pam_eps/pam_eps_passwd.c (problem with using malloc.h), and 
  telnet/telnetd/sys_term.c

        Also broken packing list which has been fixed as well.
>How-To-Repeat:
	Try installing srp port on -current system
>Fix:

    	port change as below, in shar archive format.
	this does not fix all the stupid coding errors in SRP

# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	srp
#	srp/files
#	srp/files/patch-configure
#	srp/files/patch-base::libmisc::utmp.c
#	srp/files/patch-base::pam_eps::Makefile.in
#	srp/files/patch-base::lib::utent.c
#	srp/files/patch-base::pam_eps::pam_eps_passwd.c
#	srp/files/patch-telnet::telnetd::sys_term.c-bb
#	srp/files/patch-telnet::telnetd::sys_term.c-aa
#	srp/Makefile
#	srp/distinfo
#	srp/pkg-comment
#	srp/pkg-descr
#	srp/pkg-plist
#
echo c - srp
mkdir -p srp > /dev/null 2>&1
echo c - srp/files
mkdir -p srp/files > /dev/null 2>&1
echo x - srp/files/patch-configure
sed 's/^X//' >srp/files/patch-configure << 'END-of-srp/files/patch-configure'
X--- configure.orig	Fri May 25 23:22:27 2001
X+++ configure	Wed Jul 25 13:28:17 2001
X@@ -594,6 +594,7 @@
X     INSTALL="$ac_install_sh"
X   fi
X fi
X+ac_given_INSTALL="$INSTALL"
X echo "$ac_t""$INSTALL" 1>&6
X 
X # Use test -z because SunOS4 sh mishandles braces in ${var-val}.
END-of-srp/files/patch-configure
echo x - srp/files/patch-base::libmisc::utmp.c
sed 's/^X//' >srp/files/patch-base::libmisc::utmp.c << 'END-of-srp/files/patch-base::libmisc::utmp.c'
X--- base/libmisc/utmp.c.orig	Tue Aug 21 09:00:37 2001
X+++ base/libmisc/utmp.c	Tue Aug 21 09:01:33 2001
X@@ -371,6 +371,9 @@
X 	int	found = 0;
X 	off_t	pos;
X 
X+#if defined(__FreeBSD__)
X+#define _UTMP_FILE _PATH_UTMP
X+#endif
X 	if ((fd = open(_UTMP_FILE, O_RDWR)) < 0)
X 		return;
X 
END-of-srp/files/patch-base::libmisc::utmp.c
echo x - srp/files/patch-base::pam_eps::Makefile.in
sed 's/^X//' >srp/files/patch-base::pam_eps::Makefile.in << 'END-of-srp/files/patch-base::pam_eps::Makefile.in'
X--- base/pam_eps/Makefile.in.orig	Sun Apr  8 17:11:31 2001
X+++ base/pam_eps/Makefile.in	Wed Jul 25 14:10:29 2001
X@@ -23,7 +23,7 @@
X CHKPWD = eps_chkpwd
X FAKEROOT = @prefix@
X SUPPLEMENTED = /sbin
X-SECUREDIR = /lib/security
X+SECUREDIR = /lib
X EXTRAS = -DCHKPWD_HELPER=\"$(SUPPLEMENTED)/$(CHKPWD)\"
X 
X CPPFLAGS = @CPPFLAGS@ -I../../libsrp $(USE_LCKPWDF) $(NEED_LCKPWDF) $(EXTRAS)
END-of-srp/files/patch-base::pam_eps::Makefile.in
echo x - srp/files/patch-base::lib::utent.c
sed 's/^X//' >srp/files/patch-base::lib::utent.c << 'END-of-srp/files/patch-base::lib::utent.c'
X--- base/lib/utent.c.orig	Wed Aug 15 20:50:34 2001
X+++ base/lib/utent.c	Wed Aug 15 20:54:08 2001
X@@ -47,6 +47,9 @@
X  * setutent - open or rewind the utmp file
X  */
X 
X+#if defined(__FreeBSD__)
X+#define _UTMP_FILE _PATH_UTMP
X+#endif
X void
X setutent ()
X {
END-of-srp/files/patch-base::lib::utent.c
echo x - srp/files/patch-base::pam_eps::pam_eps_passwd.c
sed 's/^X//' >srp/files/patch-base::pam_eps::pam_eps_passwd.c << 'END-of-srp/files/patch-base::pam_eps::pam_eps_passwd.c'
X--- base/pam_eps/pam_eps_passwd.c.orig	Tue Jan 22 15:19:55 2002
X+++ base/pam_eps/pam_eps_passwd.c	Tue Jan 22 15:20:39 2002
X@@ -75,7 +75,7 @@
X #include <syslog.h>
X #include <string.h>
X #include <stdarg.h>
X-#include <malloc.h>
X+#include <stdlib.h>
X #include <t_pwd.h>
X 
X #ifndef LINUX    /* AGM added this as of 0.2 */
END-of-srp/files/patch-base::pam_eps::pam_eps_passwd.c
echo x - srp/files/patch-telnet::telnetd::sys_term.c-bb
sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-bb << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-bb'
X--- telnet/telnetd/sys_term.c.orig	Tue Jan 22 15:29:34 2002
X+++ telnet/telnetd/sys_term.c	Tue Jan 22 15:30:03 2002
X@@ -1479,7 +1479,7 @@
X #if defined(OSF) || defined(ultrix) || defined(__hpux)
X 	time_t time();
X #else
X-	long time();
X+	time_t time();
X #endif
X 	char name[256];
X #ifdef	NEWINIT
END-of-srp/files/patch-telnet::telnetd::sys_term.c-bb
echo x - srp/files/patch-telnet::telnetd::sys_term.c-aa
sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-aa << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-aa'
X--- telnet/telnetd/sys_term.c.orig	Tue Aug 21 09:02:37 2001
X+++ telnet/telnetd/sys_term.c	Tue Aug 21 09:03:33 2001
X@@ -111,6 +111,9 @@
X #  else
X char	wtmpf[]	= "/usr/adm/wtmp";
X #  endif
X+#if defined(__FreeBSD__)
X+#define UTMP_FILE _PATH_UTMP
X+#endif
X #  ifdef UTMP_FILE
X char	utmpf[] = UTMP_FILE;
X #  else
END-of-srp/files/patch-telnet::telnetd::sys_term.c-aa
echo x - srp/Makefile
sed 's/^X//' >srp/Makefile << 'END-of-srp/Makefile'
X# New ports collection makefile for:	srp
X# Date created:							07/25/2001
X# Whom:									nectar@FreeBSD.org
X#
X# $FreeBSD: ports/security/srp/Makefile,v 1.2 2001/10/02 01:21:40 nectar Exp $
X#
X
XPORTNAME=		srp
XPORTVERSION=	1.7.4
XCATEGORIES=		security net
XMASTER_SITES=	http://www-cs-students.stanford.edu/~tjw/srp/source/
X
XMAINTAINER=		nectar@FreeBSD.org
X
XGNU_CONFIGURE=	yes
XCONFIGURE_ENV=	CC="${CC}" CFLAGS="${CFLAGS}" INSTALL="/usr/bin/install -C"
XCONFIGURE_ARGS=	--with-openssl=/usr				\
X				--with-zlib						\
X				--enable-loginf
X
XPORTDOCS=		Acknowledgements Copyrights LICENSE copyright.c \
X				draft-altman-rfc2942bis-00.txt draft-altman-rfc2944bis-01.txt \
X				draft-altman-telnet-fwdx-02.txt \
X				draft-ietf-tn3270e-telnet-tls-05.txt rfc2941.txt rfc2942.txt \
X				rfc2944.txt rfc2945.txt rfc2946.txt rfc2947.txt rfc2948.txt \
X				rfc2949.txt rfc2950.txt rfc2952.txt rfc2953.txt srp.ps
X
X.if !defined(NOPORTDOCS)
Xpost-install:
X.for f in ${PORTDOCS}
X	${MKDIR} ${PREFIX}/share/doc/srp
X	${INSTALL_DATA} ${WRKSRC}/docs/${f} ${PREFIX}/share/doc/srp/${f}
X	@${ECHO} share/doc/srp/${f} >> ${TMPPLIST}
X.endfor
X	@${ECHO} @dirrm share/doc/srp >> ${TMPPLIST}
X.endif
X
X.include <bsd.port.mk>
END-of-srp/Makefile
echo x - srp/distinfo
sed 's/^X//' >srp/distinfo << 'END-of-srp/distinfo'
XMD5 (srp-1.7.4.tar.gz) = 9d089682baae3448039e5f9990692410
END-of-srp/distinfo
echo x - srp/pkg-comment
sed 's/^X//' >srp/pkg-comment << 'END-of-srp/pkg-comment'
XSecure Remote Password protocol library, TELNET, and FTP
END-of-srp/pkg-comment
echo x - srp/pkg-descr
sed 's/^X//' >srp/pkg-descr << 'END-of-srp/pkg-descr'
XExcerpt from the README:  
X  SRP stands for the Secure Remote Password protocol, which is a secure
X  password-based authentication and key-exchange mechanism that can be
X  used to establish session security and mutual authentication over
X  untrusted networks without requiring an external public-key infrastructure
X  or trusted third parties.  The SRP distribution consists of a fully-
X  featured, portable library that implements SRP-based secure password
X  authentication as well as implementations of popular applications and
X  services like Telnet and FTP with support for transport security and
X  SRP.  These password-based applications leverage the strength of the
X  SRP authentication mechanism to offer fairly good protection against
X  both passive and active network attacks, which is an improvement over
X  most existing password-only techniques.
X
XWWW: http://srp.stanford.edu/
END-of-srp/pkg-descr
echo x - srp/pkg-plist
sed 's/^X//' >srp/pkg-plist << 'END-of-srp/pkg-plist'
Xbin/ftp
Xbin/login
Xbin/passwd
Xbin/su
Xbin/tconf
Xbin/telnet
Xinclude/cstr.h
Xinclude/krypto.h
Xinclude/srp.h
Xinclude/t_client.h
Xinclude/t_pwd.h
Xinclude/t_server.h
Xinclude/t_sha.h
Xlib/libkrypto.a
Xlib/libsrp.a
Xlib/pam_eps_auth.so
Xlib/pam_eps_passwd.so
Xsbin/eps_chkpwd
Xsbin/ftpd
Xsbin/telnetd
END-of-srp/pkg-plist
exit

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports->nectar 
Responsible-Changed-By: sf 
Responsible-Changed-When: Tue Jan 22 14:00:40 PST 2002 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34183 
State-Changed-From-To: open->closed 
State-Changed-By: nectar 
State-Changed-When: Tue Jan 22 14:40:43 PST 2002 
State-Changed-Why:  
I updated the port to address the issues you mention. 
srp/files/patch-base::pam_eps::pam_eps_passwd.c rev 1.1 
srp/files/patch-telnet::telnetd::sys_term.c rev 1.2 
srp/pkg-plist rev 1.3 

I did not use the port you included: 
= If you are not the maintainer, please submit patches, 
rather than entire ports.  This makes it easier to review 
changes. 
= The changes you submitted were incorrect in minor ways. 
Please check the committed changes for details, or drop me 
a line. 
= There should be a one-to-one relationship between patch 
files and source files. 

Thanks for your report! 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34183 

From: Will Andrews <will@csociety.org>
To: Trish Lynch <trish@bsdunix.net>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/34183: Update port: security/srp, various patches and fixes for compilation
Date: Tue, 22 Jan 2002 18:14:12 -0500

 On Tue, Jan 22, 2002 at 04:37:40PM -0500, Trish Lynch wrote:
 > sed 's/^X//' >srp/files/patch-configure << 'END-of-srp/files/patch-configure'
 > sed 's/^X//' >srp/files/patch-base::pam_eps::Makefile.in << 'END-of-srp/files/patch-base::pam_eps::Makefile.in'
 > sed 's/^X//' >srp/files/patch-base::pam_eps::pam_eps_passwd.c << 'END-of-srp/files/patch-base::pam_eps::pam_eps_passwd.c'
 > sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-bb << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-bb'
 
 These are trivial patches and could easily have been replaced
 with perl regexes.  They should be removed.
 
 > sed 's/^X//' >srp/files/patch-base::libmisc::utmp.c << 'END-of-srp/files/patch-base::libmisc::utmp.c'
 > sed 's/^X//' >srp/files/patch-base::lib::utent.c << 'END-of-srp/files/patch-base::lib::utent.c'
 > sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-aa << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-aa'
 
 These are fairly trivial patches but probably would have taken
 more work to do in a perl regex.  I don't care either way.
 
 Next time, submit a diff for existing ports, not a shar.  This is
 well documented in the Porters' Handbook.
 
 -- 
 wca

From: Trish Lynch <trish@bsdunix.net>
To: Will Andrews <will@csociety.org>
Cc: Trish Lynch <trish@bsdunix.net>,
	<FreeBSD-gnats-submit@freebsd.org>
Subject: Re: ports/34183: Update port: security/srp, various patches and
 fixes for compilation
Date: Tue, 22 Jan 2002 20:28:50 -0500 (EST)

 On Tue, 22 Jan 2002, Will Andrews wrote:
 
 > On Tue, Jan 22, 2002 at 04:37:40PM -0500, Trish Lynch wrote:
 > > sed 's/^X//' >srp/files/patch-configure << 'END-of-srp/files/patch-configure'
 > > sed 's/^X//' >srp/files/patch-base::pam_eps::Makefile.in << 'END-of-srp/files/patch-base::pam_eps::Makefile.in'
 > > sed 's/^X//' >srp/files/patch-base::pam_eps::pam_eps_passwd.c << 'END-of-srp/files/patch-base::pam_eps::pam_eps_passwd.c'
 > > sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-bb << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-bb'
 >
 > These are trivial patches and could easily have been replaced
 > with perl regexes.  They should be removed.
 >
 
 so each porter has to be perl clued (I understand, its just a regex,
 however, I can do it in sed) but
 executing perl from the makefile is kindof extensive too.  patch
 works well because it
 also gives a context for the changes. Why the insistence on perl?
 
 
 > > sed 's/^X//' >srp/files/patch-base::libmisc::utmp.c << 'END-of-srp/files/patch-base::libmisc::utmp.c'
 > > sed 's/^X//' >srp/files/patch-base::lib::utent.c << 'END-of-srp/files/patch-base::lib::utent.c'
 > > sed 's/^X//' >srp/files/patch-telnet::telnetd::sys_term.c-aa << 'END-of-srp/files/patch-telnet::telnetd::sys_term.c-aa'
 >
 > These are fairly trivial patches but probably would have taken
 > more work to do in a perl regex.  I don't care either way.
 >
 > Next time, submit a diff for existing ports, not a shar.  This is
 > well documented in the Porters' Handbook.
 >
 
 actually it is not (it actually is, but ....) according to this,  and I
 quote:
 
 
 ---------------------------
 
 "Now that you are happy with your port, the only thing remaining is to put
 it in the main FreeBSD ports tree and make everybody else happy about it
 too. We do not need your work directory or the pkgname.tgz package, so
 delete them now. Next, simply include the output of shar `find port_dir`
 in a bug report and send it with the send-pr(1) program (see Bug Reports
 and General Commentary for more information about send-pr(1). If the
 uncompressed port is larger than 20KB, you should compress it into a
 tarfile and use uuencode(1) before including it in the bug report
 (uuencoded tarfiles are acceptable even if the bug report is smaller than
 20KB but are not preferred). Be sure to classify the bug report as
 category ports and class change-request (Do not mark the report
 confidential!). Also add a short description of the program you ported to
 the ``Description'' field of the PR and the shar or uuencoded tarfile to
 the ``Fix'' field. The latter one helps the committers a lot, who use
 scripts for the ports-work.
 
 One more time, do not include the original source distfile, the work
 directory, or the package you built with make package.
 
 Note: In the past, we asked you to upload new port submissions in our FTP
 site (ftp.FreeBSD.org). This is no longer recommended as read access is
 turned off on the incoming/ directory of that site due to the large amount
 of pirated software showing up there.
 
 We will look at your port, get back to you if necessary, and put it in the
 tree. Your name will also appear in the list of ``Additional FreeBSD
 contributors'' in the FreeBSD Handbook and other files. Isn't that
 great?!? :-)
 
 Note: You can make our work a lot easier, if you use a good description in
 the synopsis of the problem report. We prefer something like ``New port:
 <short description of the port>'' for new ports and ``Update port:
 <category>/<port> <short description of the update>'' for
 port updates. If you stick to this scheme, the chance that one takes a
 look at your PR soon is much bigger."
 
 ------------
 
 so the ports handbook *specifically* asks for shar's as the preferred
 submittal method. :) or uuencoded tar file (if over 20k)
 
 However, buried deep within is this:
 
 ------------
 
 When you notice that a port is out of date compared to the latest version
 from the original authors, first make sure you have the latest port. You
 can find them in the ports/ports-current directory of the FTP mirror
 sites. You may also use CVSup to keep your whole ports collection
 up-to-date, as described in the Handbook.
 
 The next step is to send a mail to the maintainer, if one is listed in the
 port's Makefile. That person may already be working on an upgrade, or have
 a reason to not upgrade the port right now (because of, for example,
 stability problems of the new version).
 
 If the maintainer asks you to do the upgrade or there is not any such
 person to begin with, please make the upgrade and send the recursive diff
 (either unified or context diff is fine, but port committers appear to
 prefer unified diff more) of the new and old ports directories to us
 (e.g., if your modified port directory is called superedit and the
 original as in our tree is superedit.bak, then send us the result of diff
 -ruN superedit.bak superedit). Please examine the output to make sure all
 the changes make sense. The best way to send us the diff is by including
 it via send-pr(1) (category ports). Please mention any added or deleted
 files in the message, as they have to be explicitly specified to CVS when
 doing a commit. If the diff is more than about 20KB, please compress and
 uuencode it; otherwise, just include it in the PR as is.
 
 Note: Once again, please use diff(1) and not shar(1) to send updates to
 existing ports!
 
 --------------
 
 
 which is correct, however there should be something pointing to that in
 the submittal section, since that section *does* cover changes to ports as
 well.
 
 Also one would caution you *against* requiring perl in packages, given
 that the person may not be well versed in perl :)
 
 (I could do it, I just see no real advantage one over the other, actually,
 other than a few bytes of storage, which with 7000 ports, I doubt less
 than 1k is going to make a difference, this port was 8k in all)
 
 > --
 > wca
 >
 
 please explain, and show grasshopper the way... "do this" with no actual
 reason doesn't help too much :)
 
 
 -Trish
 
 
 --
 Trish Lynch					trish@bsdunix.net
 FreeBSD						The Power to Serve
 Ecartis Core Team				trish@listmistress.org
                    http://www.freebsd.org
 
 

From: Will Andrews <will@csociety.org>
To: Trish Lynch <trish@bsdunix.net>
Cc: Will Andrews <will@csociety.org>,
	FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/34183: Update port: security/srp, various patches and fixes for compilation
Date: Tue, 22 Jan 2002 20:42:06 -0500

 On Tue, Jan 22, 2002 at 08:28:50PM -0500, Trish Lynch wrote:
 > so each porter has to be perl clued (I understand, its just a regex,
 > however, I can do it in sed) but
 > executing perl from the makefile is kindof extensive too.  patch
 > works well because it
 > also gives a context for the changes. Why the insistence on perl?
 
 1) Reduction of inode count in ports checkouts while file exists;
 2) Reduction of inode count in cvs servers forever;
 3) Lower maintenance cost.
 
 Perl in itself is not required, just some RE.  You could use sed
 if you so desired, but sed can't do in-place regexes, unlike perl.
 The RE I use outlive most patches I've used because they match
 more specific context.
 
 > actually it is not (it actually is, but ....) according to this,  and I
 > quote:
 
 You didn't have to quote the entire thing.  The way I read it
 makes it sound like the first part you quoted pertains to -new-
 ports, and the second part pertains to -current- ports.
 
 Although...
 
 > Note: You can make our work a lot easier, if you use a good description in
 > the synopsis of the problem report. We prefer something like ``New port:
 > <short description of the port>'' for new ports and ``Update port:
 > <category>/<port> <short description of the update>'' for
 > port updates. If you stick to this scheme, the chance that one takes a
 > look at your PR soon is much bigger."
 
 ..this section should be put someplace where it's obvious that it
 contains advice pertinent to both sections you quote.
 
 Regardless, I agree that the information is a little deeply
 nested, and the porters' handbook could use a slight cleanup.
 
 > Also one would caution you *against* requiring perl in packages, given
 > that the person may not be well versed in perl :)
 
 In *packages*?  What are you smoking?  :-)
 
 Like I said, it's not particularly important and it's possible
 that I might write a simple macro so one could specify REs to
 apply to a set of files without needing to specify the command to
 apply with.  The syntax for applying REs is different for perl
 vs. sed, unfortunately.  So if at some point in the future perl
 doesn't come with FreeBSD, it is trivial to convert all the perl
 REs currently used in ports to sed REs.  I just use the right
 tool for the job.
 
 > (I could do it, I just see no real advantage one over the other, actually,
 > other than a few bytes of storage, which with 7000 ports, I doubt less
 > than 1k is going to make a difference, this port was 8k in all)
 
 Bytes don't matter.  Inodes do, performance wise.  Ports require
 an insanely large number of them already.  Inode count was the
 whole reason for merging the patches/ and pkg/ subdirs of ports
 into the main port dir roughly a year and a half ago.
 
 -- 
 wca
>Unformatted:
