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 Date: Tue, 11 Feb 2003 23:37:47 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygpath bug in version 1.25 -- Fundamental Change in the Behaviour of Cygpath Message-ID: <20030212043747.GA22968@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <012501c2d229$5fd434f0$78d96f83 AT pomello> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012501c2d229$5fd434f0$78d96f83@pomello> User-Agent: Mutt/1.5.1i On Tue, Feb 11, 2003 at 11:57:45PM -0000, Max Bowsher wrote: >Igor Pechtchanski wrote: >> On Tue, 11 Feb 2003, Newton, Doug wrote: >> >>> If this change is what is desired by the majority, that is fine. >>> BUT, it should have been made clear that the fundamental behaviour >>> of cygpath had changed. I have many scripts that no longer work. >>> Even the jakarata ant tool's start-up script now mangles the >>> classpath because of this change in behaviour. >> >> This change makes the output correct. I suppose that would be >> something desired by the majority... > >Yet technical correctness has come at the price of usability and >functionality. >E.g. You cannot convert to --mixed style from --windows style with --path. Use sed if you want to change backslashes to slashes. >> It makes an assumption that the format is Windows. Otherwise, >> there'd be no need to convert to Unix format... > >Of course, if you simply wanted to *ensure* that the path was in unix >format... you're stuck. Cygwin provides *UNIX* functionality, remember? case "$CLASSPATH" in *;*) CLASSPATH=`cygpath --path --unix "$CLASSPATH"` ;; */*) ;; # do nothing *) CLASSPATH=`cygpath --path --unix "$CLASSPATH"` ;; esac I'm not saying that the above is foolproof. I haven't even tested it. However, as usual, if everyone would put as much effort into thinking about solutions as they did with complaining about the terrible terrible problem, they'd be farther along the path of a solution. For the record, the old code was broken and buggy. It "worked" in an undocumented fashion. And, perhaps more importantly, the change was introduced in November. It is now February. Get used to it and move on. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/