This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

cygwin coreutils-5.3.0-4 rm change breaks Libtool


From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]
Sent: Mittwoch, 13. April 2005 03:50
To: cygwin@cygwin.com
Subject: cygwin Digest 13 Apr 2005 01:49:36 -0000 Issue 4198

cygwin coreutils-5.3.0-4 rm change breaks Libtool
	106161 by: ericblake@comcast.net (Eric Blake)
	106164 by: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
	106166 by: Charles Wilson <cygwin@cwilson.fastmail.fm>
	106167 by: Eric Blake <ebb9@byu.net>


Hi all,

sorry if this comment is stupid, I have not at all been involved in system
design so far. Anyway, from a user's point of view: commands like rm are
intrinsically dangerous since they might destroy something. Therefore I very
much prefer that I know what exactly rm will do - typing "rm foo" I would very
much prefer just to remove foo, and not, eventually, foo.exe, if this exists
and foo does not. Otherwise I would have to think about this, check the
directory, etc, which makes work more strenuous and susceptible to mistakes.
With commands like stat there is certainly no comparable problem to do
extension magics, since you usually do not immediately remove files or links.

Wolfgang





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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]