From owner-freebsd-hackers Fri Sep 24 7:54: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.kolumbus.fi (smtp1.kolumbus.fi [193.229.0.36]) by hub.freebsd.org (Postfix) with ESMTP id 1568F14D4F for ; Fri, 24 Sep 1999 07:53:58 -0700 (PDT) (envelope-from jsalomaa@saunalahti.fi) Received: from kone (i93i2hel.dial.kolumbus.fi [193.229.126.93]) by smtp1.kolumbus.fi (8.9.0/8.9.0) with ESMTP id RAA05368; Fri, 24 Sep 1999 17:52:46 +0300 (EET DST) Date: Fri, 24 Sep 1999 17:52:57 +0300 (EEST) From: Jaakko Salomaa X-Sender: jsalomaa@kone.kala.net To: "Daniel C. Sobral" Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get In-Reply-To: <37EB34AE.35683512@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Sep 1999, Daniel C. Sobral wrote: > > This is quite interesting and I'm looking at it now. Just one quick > > question though - why did you "roll your own" ftp I/O handling instead > > of simply using fetch(3) or ftpio(3)? > > Alas, it also seems to have a "default" ftp site. I don't think > that's a good idea (remember CHANGE_THIS.freebsd.org :). An > environment variable would do just as well, except... this is the > kind of tool like to be used by clueless users, which are the ones > most likely to really want a default site. It's designed to be easy to use, so it first checks -s parameter, then PKGSERVER environment variable, then the machine's toplevel domain. If the toplevel domain contains only two letters it attemps to use ftp..freebsd.org, else it defaults to ftp.freebsd.org and prompts whether the user wants to use it. BTW, I'm now utilizing ftpio(3) instead of my own kludge, I'll probably send a new message to -hackers when the new version is ready. (I'm going to spend a few days somewhere else.) May you live long and prosper. Jaakko Salomaa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message