X-Spam-Check-By: sourceware.org Message-ID: <5753856.post@talk.nabble.com> Date: Thu, 10 Aug 2006 15:32:33 -0700 (PDT) From: infoterror To: cygwin AT cygwin DOT com Subject: Re: Cygintl-3.dll was not found In-Reply-To: <20060809210958.GA3815@trixie.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <58fb98730601070837k26ad68f5l AT mail DOT gmail DOT com> <43BFEFB9 DOT EA24C5B4 AT dessent DOT net> <5718434 DOT post AT talk DOT nabble DOT com> <003001c6bb9a$4e15b140$a501a8c0 AT CAM DOT ARTIMI DOT COM> <5732487 DOT post AT talk DOT nabble DOT com> <20060809210958 DOT GA3815 AT trixie DOT casa DOT cgf DOT cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 >FYI, you seem to be implying that this is some sort of UNIX installer >when it really is just a home-grown Windows installer designed to handle >Cygwin's needs. I have no problems with the user interface but I do >understand that some Windows users find it unintuitive. When installing under windows, it makes sense to use the standard (.msi) and style of windows installers. It is rude to go into a room full of people speaking Tagalog and insist they speak English; similarly, when one wants something to work under windows, it should adapt to that standard. >I disagree. Not all packages install in "c:\Program Files" and putting >Cygwin's root directory there would mean extra typing, potential >"filename with spaces" problems, and, most importantly, it would mean 10 >extra characters eaten from the MAX_PATH limit. Also, as is pointed out >later in this thread, there is a whole filesystem underneath the >c:\cygwin directory. Right or wrong, I've always considered Cygwin to >be sort of a parallel to the Windows directory. To a windows user, it is an application. Installing all program files into c:\Program Files provides the user a consistent interface. Some in the corporate world seek to mystify this, but their apps are acknowledged by experienced windows people as errant. Another way to put this: if you were a corporate MIS/IT/etc department head and you wanted to keep machines organized, you would probably have all software installed in the same location. Makes backup easy. Makes it immediately discernible what must be moved/modified if there's a problem with a machine. >You can, of course, choose your own location, however. I don't see why >this should be a big issue for anyone who installs Cygwin. If they know >about "c:\Program Files" and think that's the place that cygwin should >go, they are welcome to put things there. Instead of making more work for them to do it right, why not just do it right from the start? >What kind of problems do you think are being caused by installing to >"c:\cygwin" and/or what kind of problems would be solved by installing >to "c:\Program Files\cygwin"? Please see above. -- View this message in context: http://www.nabble.com/Cygintl-3.dll-was-not-found-tf869884.html#a5753856 Sent from the Cygwin Users forum at Nabble.com. -- 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/