X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 16 Sep 2009 21:44:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: goldstar? Re: cygdrive prefix Message-ID: <20090917014400.GB25602@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <182640b4a6730dafadd266e0cfc9d9bf AT mail DOT smartmobili DOT com> <416096c60909161406tbfd73ey7a5b9510e7f97762 AT mail DOT gmail DOT com> <4AB1924F DOT 80005 AT shaddybaddah DOT name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AB1924F.80005@shaddybaddah.name> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 On Thu, Sep 17, 2009 at 11:35:11AM +1000, Shaddy Baddah wrote: >Hi, > >Andy Koppe wrote: >> 2009/9/16 Thorsten Kampe >> >>> you shouldn't install Cygwin >>> directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the >>> Windows root folder structure mixed. >>> >> >> And where exactly is the harm in that? Apple certainly don't see a >> problem with it, with the likes of /Applications and /Users living >> happily alongside /bin and /var. Actually it makes for a much more >> integrated Cygwin user experience not to have to mentally switch >> between different roots and add those \cygwin and /cygdrive (or >> whatever) prefixes when accessing stuff from the other side of the >> fence. >> >I don't run an Apple computer OS, but my observation is that they are >based around a packaging system called 'port'? If true, that >undermines your argument somewhat. Because then you are even with >Linux/most unices, which of course carefully drop all exes into bin, >libraries into lib, etc. In this case there is nothing wrong dropping >everything into a single bin,lib,.. dir as you say, because there is a >package management system there to hold manifests, handle collisions, >allow uninstalls etc. etc. But without a package management system, >you are asking for trouble. > >In this case, although cygwin has a package management system, it is >not going to manage the non-cygwin stuff dropped into c:/bin,lib, >etc. And that means if a user goes and installs something like msys >under the same mode of thinking, they won't stand much chance of >getting support if they come running here to complain about make or >someother app behaving unexpectedly because they've now got a /bin >directory tainted with non-cygwin exes. At least they would be very >unpopular for wasting the list's time. > >Of course, if the user knows what they are doing, either implementing >their own package management functions or diligently acting as their >own package manager, there is no reason for having c:/ as cygwin root >not to work. It's just highly discouraged for the reasons I've given. Wow. Nice summation of the reasons for the need for a c:\cygwin. Can I get a goldstar here? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple