Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: [Mingw-users] Cygwin Full download in one big archive ? From: Robert Collins To: Richard Campbell Cc: "'cygwin@cygwin.com'" In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-o/MhjOEnSkMKb0Ma8dlk" Date: 06 Dec 2002 09:20:28 +1100 Message-Id: <1039126829.13185.121.camel@lifelesswks> Mime-Version: 1.0 --=-o/MhjOEnSkMKb0Ma8dlk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2002-12-06 at 01:39, Richard Campbell wrote: > >Impractical. As I said, almost 100% of people won't want 100% of package= s. >=20 > It might be interesting to poll in some way, considering how often this=20 > comes up. I suspect more than "almost 0%" might want a 1-button,=20 > overnight-style install. I agree with you with regards to what folk may want. The modular install is about choice and efficiency. There is *no* reason that a 1-button overnight-style install cannot be achieved using setup.exe. Patches accepted gratefully. With regards to having a monolithic download however... Some back-of-a-postcard sums: monolithic install 577MB install. 1 update to a package a week, 1 new 577MB install file created each week. longest period without updating - 2 months. this would mean an average of ~280MB per month downloading updates. modular install 577MB total download size 1 update to a package a week, 1 new modular install (avg ~5MB) created each week. longest period without updated - 2 months. this would mean an average of ~20MB per month downloading updates. Seems pretty clear to me, that for anyone on a slow link, or anyone charged by volume, that the modular install is much more efficient. Rob --=20 --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- --=-o/MhjOEnSkMKb0Ma8dlk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA979EsI5+kQ8LJcoIRAiLRAKDVlNPeGUuZduNgNJieMChZ2Jx5XQCgxSRR Z7Cu7ArhnQu62PGW9wvQ8X4= =RCad -----END PGP SIGNATURE----- --=-o/MhjOEnSkMKb0Ma8dlk--