Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <005301c073f1$46aa6aa0$0200a8c0@lifelesswks> From: "Robert Collins" To: , References: <000001c073ef$1f26fa40$9b3770c2 AT fifer> Subject: Re: Distributed Perl 5.6.1 bug report. Date: Mon, 1 Jan 2001 23:49:21 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Fantastic. I can update the scripts that were broken to use a backup extension. reagarding the cygwin error - is there some reason you can't assume a .orig extension for the cygwin platform? Or even use a temp backup extension and then unlink the backup file when finished? I'm just thinking along maximum transparency for all the unix scripts out there. (The ones I know of are MRTG's configure and install scripts, some useful cvs scripts.. and I'm not even scratching the surface). Anyway you've given me a workaround, for which I am very grateful. Rob ----- Original Message ----- From: "Eric Fifer" To: "'Robert Collins'" ; Sent: Monday, January 01, 2001 11:33 PM Subject: RE: Distributed Perl 5.6.1 bug report. > > Robert Collins wrote: > > Do the perl 5.6.1 tests include inplace edit testing? > >I ask because the perl >available for download via 'Cygwin Setup' is > >deleting files when using inplace edits, rather than editing the file. > > To do inplace editing you will need to provide a backup > extension (-i.orig). Apparently none of the tests check > inplace editing with a null backup extension. You found > a bug with the Perl Cygwin port and I will fix it, but > the end result will be this error message: > > Can't do inplace edit without backup > > Also, just so you know what is going on. The Perl code > is taking advantage of the Unix feature where you can > unlink an open file and the file disappears from the > file system. With Cygwin this didn't really work as > expected and it ended up clobbering your file. The > "Permission Denied" message doesn't have anything to > do with your permissions, but is the error you get > when you stat() a file that has been deleted but is > still open. > > Hope this helps. > > Eric Fifer > > > -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple