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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 16 Sep 2003 18:05:07 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Rolf Campbell cc: cygwin AT cygwin DOT com Subject: Re: Setup installation order? In-Reply-To: Message-ID: References: <20030916174957 DOT 2533 DOT qmail AT web21405 DOT mail DOT yahoo DOT com> Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 16 Sep 2003, Rolf Campbell wrote: > Igor Pechtchanski wrote: > > > On Tue, 16 Sep 2003, Rick Rankin wrote: > >>I ran into a situation I hadn't seen before a few days ago when I used > >>setup to update my Cygwin installation from 1.5.3 to 1.5.4. What > >>happened was that there were several packages, in addition to > >>cygwin-1.5.4, that had updates available. Setup downloaded the updates, > >>then uninstalled the old packages, including cygwin-1.5.3. When it went > >>to install the updates, cygwin-1.5.4 was *not* the first package that > >>got installed, so any postinstallion scripts failed with a dialog box > >>from the O/S saying that "Windows cannot find cygwin1.dll in >>list>" until after cygwin itself was updated. After setup installed the > >>cygwin package, the rest of the postinstall scripts ran fine. > >> > >>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 dependency processing, yet. So far, I haven't found anything related > >>via Google searches, either. > >> > >>--Rick > > > > > > The setup program simply performs a topological sort of the package > > dependence graph, and then traverses the packages in that order. Of > > course, since the graph is cyclic, topological order is not unique. In > > any case, the postinstall scripts should run after *all* the packages are > > unpacked, so you shouldn't be missing cygwin1.dll on postinstall. > > > > However, preremove scripts are run just before the corresponding package > > is removed (in alphabetical order, IIRC). This presents a problem, but > > noone so far has considered it a large enough problem to invest the effort > > in a fix. It's likely that you saw this particular problem in your > > upgrade. . > > Igor > > Wouldn't it make sence to call each preremove script before any packages > are actually removed? It would make sense. It's currently not done that way. PTC. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/