From owner-freebsd-ports Mon Oct 13 19:49:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14684 for ports-outgoing; Mon, 13 Oct 1997 19:49:25 -0700 (PDT) (envelope-from owner-freebsd-ports) Received: from ppp1643.on.sympatico.ca (ppp1643.on.sympatico.ca [206.172.249.107]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14667; Mon, 13 Oct 1997 19:49:16 -0700 (PDT) (envelope-from tim@ppp1643.on.sympatico.ca) Received: from localhost (tim@localhost) by ppp1643.on.sympatico.ca (8.8.7/8.8.7) with SMTP id WAA00474; Mon, 13 Oct 1997 22:47:41 -0400 (EDT) (envelope-from tim@ppp1643.on.sympatico.ca) Date: Mon, 13 Oct 1997 22:47:40 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: James Raynard cc: Satoshi Asami , ports@FreeBSD.ORG, ports-jp@FreeBSD.ORG Subject: Re: ports/4304 ports Recommendation re. Ports Collection In-Reply-To: <19971013225014.30732@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [cc adjusted off -committers] [subj changed from "Administrative notice: 8 days to 2.2.5"] On Mon, 13 Oct 1997, James Raynard wrote: > I know this is probably too late for 2.2.5, but I thought it might be > worth mentioning anyway. What do people think to putting the size of > the tarball somewhere in the skeleton for each port? This would be See the pr o [1997/08/14] ports/4304 ports Recommendation re. Ports Collection It should have a rather lengthy follow-up by me discussing the idea. > Something along the lines of:- > > --- bsd.port.mk Mon Oct 13 20:07:19 1997 > +++ bsd.port.mk.new Mon Oct 13 20:18:53 1997 > @@ -389,6 +389,8 @@ > MD5?= md5 > .endif > MD5_FILE?= ${FILESDIR}/md5 > +LS?= ls -s > +SIZES_FILE?= ${FILESDIR}/sizes It would go over better if you could conceive of a way to do this without adding another files/file file. Oddly enough, though, I was just thinking that ports/4304 should be closed RSN unless someone coughed-up some code... -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster.