Date: Wed, 15 Oct 1997 17:19:23 +0930 (CST) From: Kristian Kennaway <kkennawa@physics.adelaide.edu.au> To: andreas@klemm.gtn.com (Andreas Klemm) Cc: asami@cs.berkeley.edu, jraynard@jraynard.demon.co.uk, committers@FreeBSD.ORG, ports@FreeBSD.ORG, ports-jp@FreeBSD.ORG Subject: Re: 8 days until 2.2.5... Administrative notices. Message-ID: <9710150749.AA14643@bragg> In-Reply-To: <19971015000853.28485@klemm.gtn.com> from "Andreas Klemm" at Oct 15, 97 00:08:53 am
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Oct 14, 1997 at 02:08:57AM -0700, Satoshi Asami wrote: > > * On Mon, Oct 13, 1997 at 03:56:57AM -0700, Satoshi Asami 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 > > * very helpful for people with poor Internet connectivity. Quite a few > > * times I've thought about installing a port, but wasn't sure how long > > * a download I was letting myself in for. Currently, the only way this > > * can be done is by looking on the master site. > > > > Hmm. That is an interesting idea. > > Another thing is, that it would be fine, if fetch would show > more infos about the download progress. Percent of downloaded > data, performance (K/sec), estimated time remaining. > > When downloading large files it would be extremely useful. This is why I prefer ncftp v2.x as my ftp client - I wonder if it would be possible to replace fetch with ncftp as the ports file-collection mechanism if fetch doesnt have these capabilities (and they cant easily be added). Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9710150749.AA14643>