This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: general setup.exe status incl network install [was Re: setup ChangeLog IniDBBuilder.h IniDBBuilderPac ...]
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 17 Dec 2009 16:11:32 +0000
- Subject: Re: general setup.exe status incl network install [was Re: setup ChangeLog IniDBBuilder.h IniDBBuilderPac ...]
- References: <20091213192343.10516.qmail@sourceware.org> <20091216085611.GJ8059@calimero.vinschen.de> <4B28ED95.1020806@gmail.com> <20091216143717.GA3024@calimero.vinschen.de> <4B298A58.9020304@gmail.com> <20091217094001.GQ8059@calimero.vinschen.de> <20091217100238.GB14229@calimero.vinschen.de>
Corinna Vinschen wrote:
> The question is probably, do we need an unlink-while-you-still-have-an-
> open-handle-to-the-file functionality which also works on shares?
Well, if we're going to support installing to a root on a network drive at
all, it's not going to run very well without it.
> Right now it works like this: If no recycle bin exists, create it.
> Move the file to the bin and set the delete disposition if possible.
> Recycle bins only exist on local drives, so shares are out of luck.
> Two possible workarounds come to mind:
>
> - Rename the file to something really terrible within the same dir.
>
> - Potential name collisions (need a good algorithm for weird filenames)
> - Disallows to remove the parent dir
> + Simple
This one seems like the best bet. Can we just reuse mkstemp?
cheers,
DaveK