Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <311010-2200442205467993@cantv.net>
Reply-To: rodmedina AT cantv DOT net
From: "Rodrigo Medina" <rodmedina AT cantv DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: Wishlist additions for setup.exe
Date: Tue, 20 Apr 2004 01:46:08 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1

Hi all,

My whishes for SETUP:

1- In the list of packages include its size. It is very important
for people with slow connexions, so they can easily program
what to download and in which order. For example you may decide
not to download an updated 16MB fonts package with minor changes.
Right now you discover that the package has 16MB only after the
downloading of that package has started. Then you have to abort
setup and start again. (This is related to point 2-).

2- When you are downloading into a temporal directory, SETUP
downloads the packages even if they are already in the temporal
directory but are still not installed. I think this is a real  nuisance.
 Consider the case that for some reason the downloading
is interrupted (this is likely to happen if you have a slow connexion).
Say you have already downloaded 90% of the packages (that could take
hours). SETUP starts again from the beginning. This can lead to a
never ending process.
You have two choices:
a) To install what was already downloaded before starting a new
setup-downloading session. This in some cases could be dangerous
when you are installing packages that require some other package
that you have not still downloaded.
b) To look at the files in the temporal directory to check what
files are already downloaded and mark those files KEEP (or SKIP)
in the package list. Should not be SETUP an automatic process?

I think that to solve these two problems require minor changes
of SETUP and would really improve its performance.

bye,

Rodrigo Medina
			  	

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/