From owner-freebsd-ports Mon Apr 26 1:20:54 1999 Delivered-To: freebsd-ports@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id E23B414A2F for ; Mon, 26 Apr 1999 01:20:36 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 28097 invoked by uid 1003); 26 Apr 1999 10:22:11 -0000 Date: Mon, 26 Apr 1999 10:22:11 +0000 From: Neil Blakey-Milner To: David O'Brien Cc: ports@FreeBSD.ORG Subject: Re: Comments on addition of local distfile repository Message-ID: <19990426102211.A26678@rucus.ru.ac.za> References: <199904250236.WAA87397@istari.home.net> <19990426003732.B53806@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990426003732.B53806@dragon.nuxi.com>; from David O'Brien on Mon, Apr 26, 1999 at 12:37:32AM -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon 1999-04-26 (00:37), David O'Brien wrote: > > I'm wondering if there is any interest in adding a "local distfile" > > repository to the bsd.port.mk file. I would envision using this to > > maintain the "hand transferred" distfiles, as well as a convenient > This could be quite useful. Hi, I have patches doing a similar thing at home, except I mangled DISTDIR to allow multiple directories. Of course, this way may seem easier, but I have two nits. Firstly, the file is copied from the local distfile repository into /usr/ports/distfiles, which uses space. (which is not necessarily a bad way to do it - also see 'blow away distfiles' below) Secondly, some people use wget or similar to fetch files, and wget for one doesn't seem to understand file:/. While I'm at it, is there any need for an option to blow away distfiles once they're extracted? (or, perhaps I should ask if that option exists already) This would be useful in a large environment with many FreeBSD boxen where you'd like to maintain a central distfiles server, which "caches" your hits via a web script (which I've sort-of got working). The script fetches the file if it's not on disk, saves it to disk, and returns it to the client. There are some slight timing problems with this atm, though. (this could be achieved via NFS, of course, but that isn't always an option, and would require r/w access) Or, of course, if you have bandwidth to burn, and local space is a problem. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message