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: <01b201c4cb1f$a6592020$e6ec6f83@robinson.cam.ac.uk>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <bbf4cf4f04111205571222c5ed AT mail DOT gmail DOT com> <41955C18 DOT 19EC87EB AT dessent DOT net> <bbf4cf4f0411141906522f04c8 AT mail DOT gmail DOT com> <4198234F DOT 1B70A3AF AT dessent DOT net> <419899A2 DOT 5070806 AT x-ray DOT at>
Subject: Re: FYI: Reboot is needed after a failed setup.
Date: Mon, 15 Nov 2004 14:28:46 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
X-Cam-AntiVirus: No virus found
X-Cam-SpamDetails: Not scanned
X-IsSubscribed: yes
Note-from-DJ: This may be spam

Reini Urban wrote:
> Brian Dessent schrieb:
>> Stephen More wrote:
>>> I am willing to try an add this logic. Where is the source for setup.exe 
>>> ?
>>>
>>> I am looking through CVS and I am not finding the setup code:
>>> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/?cvsroot=src
>>
>> You can find details of building setup.exe at
>> <http://sources.redhat.com/cygwin-apps/setup.html>.
>>
>> If you proceed, you should join the cygwin-apps list where setup.exe
>> development is on-topic and coordinate with the other setup.exe
>> maintainers.  I believe that means Max Bowsher currently (previously
>> Robert Collins) with patches also coming from Reini U., Igor P., Gary
>> V.S., et al.
>
> Added as http://sourceware.org/bugzilla/show_bug.cgi?id=548

Thanks for taking care of bugzilla, Reini!

Rather than special-casing the cygwin dll, I think a better solution would 
be to run all preremove scripts, then perform all file deletions and 
extractions, then run all postinstall scripts.

This would solve similar problems involving other dlls too.

Please transfer further discussion to the cygwin-apps mailing list.

Thanks,

Max.


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