Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<420AE1B9.60408@tlinx.org>
Date:	Wed, 09 Feb 2005 20:23:21 -0800
From:	linda w <cygwin AT tlinx DOT org>
User-Agent:	Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version:	1.0
To:	"'Cygwin List'" <cygwin AT cygwin DOT com>
Subject:	[Fwd: Re: bug in setup.exe?]
X-IsSubscribed:	yes

      <Dang bottom posters>: [It depends on what email client you use
    to read with -- if one is using a GUI, the top of the message is
    displayed first. This forces "scrolling" (or turning) to the last
    page of an email -- reading it in reverse order...how lame is that?
    Even if you use a tty mode email interface, few of them display the
    last page first. Putting the new content at the bottom would force
    scrolling through a long duplicate that one might not need if one
    already knows context -- but then one doesn't really know if one
    needs the quoted context until one has read the new content -- thus,
    unless it is a very small quote, it's usually more direct to put new
    content at the top.]

    However, regarding the topic at hand -- "setup", special casing
"cygwin-dll" may fix this problem, but it'd be a kludge. Suppose a
pre-uninstall script for squid has a dependency on something in coreutils,
you update coreutils and squid, but going alphabetically, coreutils gets
uninstalled first. The squid pre-uninstall scripts fail because the
core-utils were removed before updating.

     What I would suggest is ordering the uninstalls via dependencies, as,
I would assume (?), setup would do when installing -- i.e. it would install
packages that depend on other packages after installing the prerequisites.

    In the case of removals, packages that have pre-reqs would be ordered
to be removed *before* any pre-reqs are uninstalled. This way, your system
should never be in a state where 1) pre-reqs for a package are removed
before the package that depends on them, or 2) pre-reqs are not already
installed before a package that depends on them is installed.

    I'm sure "PTC" would apply...;-)

Linda

Swenson, Eric wrote:

 >Thanks, Igor. Would another possible solution be to have setup special 
case
 >*only* the cygwin-dll package?
 >


--
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/

- Raw text -