Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: Setup installation order? From: Robert Collins To: Rick Rankin Cc: cygwin AT cygwin DOT com In-Reply-To: <20030916174957.2533.qmail@web21405.mail.yahoo.com> References: <20030916174957 DOT 2533 DOT qmail AT web21405 DOT mail DOT yahoo DOT com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ryfsyEUZGYHK3Dwm0gRg" Message-Id: <1063746087.1162.303.camel@localhost> Mime-Version: 1.0 Date: Wed, 17 Sep 2003 07:01:27 +1000 --=-ryfsyEUZGYHK3Dwm0gRg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-09-17 at 03:49, Rick Rankin wrote: > Is the cygwin package given any special consideration during the install > process (e.g., last to be uninstalled, first to be (re)installed), or is = this > something that's expected to be handled by the dependency list? I've been > perusing the setup sources, but I haven't quite figured out the dependenc= y > processing, yet. So far, I haven't found anything related via Google sear= ches, > either. Setup performs removals, replacements, new installs, in that order. Once all file copies are complete, postinstall scripts are run, in topological order (using strongly connected graph traversal). So you problem was most likely during the replacement phase.=20 The setup.log.full and setup.log would be essential to diagnose the problem. Rob --=20 GPG key available at: . --=-ryfsyEUZGYHK3Dwm0gRg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/Z3onI5+kQ8LJcoIRAlulAKC+uoVItYjGSozr71JSdiDvEBULEwCgiJuv O/kdancf97VZFsWQqPD6cOY= =zjqb -----END PGP SIGNATURE----- --=-ryfsyEUZGYHK3Dwm0gRg--