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: Thu, 17 Apr 2003 16:48:37 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Completely removing cygwin (was Re: A request?) Message-ID: <20030417204837.GC16070@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030417172623 DOT GB12623 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Apr 17, 2003 at 02:20:03PM -0400, Rick Kane wrote: >Turning the topic in another direction (I hope). When you start a new topic, please start a new thread. cgf >What I've been trying to >do is figure out how to totally remove cygwin from a machine before I do >another install. This suggests tha I could delete the cygwin directory and >the HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions from the registry. Is >there anything else? Where are all the places setup.exe looks to decide >what is already installed (and what version)? I'd like to delete those >files too. I'm just trying to do the experiment of a "clean" install. > >Thanks in advance for any help you can provide. > >> -----Original Message----- >> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf >> Of Christopher Faylor >> Sent: Thursday, April 17, 2003 1:26 PM >> To: cygwin AT cygwin DOT com >> Subject: Re: A request? >> >> >> On Thu, Apr 17, 2003 at 09:43:21AM -0400, Fletcher, Bob (GEAE, IT) wrote: >> >I'm a bit late to this discussion, but I'll jump in anyway. >> > >> >To the original question; I'd like to violate group etiquette and throw >> >in a big "Me to". Having a cleaner versioning process would be a big >> >benefit to cygwin. >> >> You're missing an IMO, there. >> >> >Also to the original question, a suggestion. I have the same problem. >> >I've taken the approach of running 'setup' on a box, then capturing the >> >files, my preferred mount points, path settings and anything else I >> >want to change, and building a Microsoft format "msi' package. I can >> >put this on a server and distribute it to internal users and they get >> >exactly my configuration. BTW, all you really need is a zip of the >> >cygwin directory and .reg file dump of >> >HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions The MSI is just a bit >> >easier to install, and I can pput in the shortcuts for people. >> >> Great. You have a solution. This isn't hard. There are many ways to >> make this work. >> >> The problem seems to be that people want someone else to do the work for >> them. While I can fully comprehend why you'd want someone to spend a >> lot of time coming up with a "stable" release so that you wouldn't have >> to, and how much of a benefit this could be to some folks, the simple >> fact is that this isn't something that I want to do. One could consider >> this unreasonable, I suppose, except for the oft-stated fact that this >> is a volunteer project and I really don't have to do be doing anything >> at all. I *am* supplying you with valuable software at no cost to you, >> though. Currently, this is the limit of my largesse. >> >> Cygwin is a strange environment. It has many users and few contributors. >> Probably that's because Red Hat is involved and people, unconsciously or >> consciously think that somehow Red Hat is or should be footing the bill. >> Or, maybe it's because the expertise level isn't high enough since >> we're talking about a Windows environment. >> >> However, to a very large degree this is a volunteer process rather than >> a voting process. If you think "stable" releases are a good idea, then >> I will gladly appoint you the cygwin stable release maintainer, I'll set >> you up with disk space on sources.redhat.com and you can start doing >> your magic. I will set you up with a mailing list, if you want. >> >> I may offer an opinion or two as you ramp up but I probably won't change >> the way we're currently doing releases or development, though. >> >> >Third, in response to cgf >> >>Sorry but you are not a customer. You're a user. There is a subtle >> >>difference. Being a customer implies some seller/buyer relationship >> >>which would entitle you to some kind of service from the seller. >> >>Cygwin is offered as-is to you with nothing guaranteed other than you >> >>get the source. >> > >> >I'd love to be a customer! I keep asking Redhat about it, but there's >> >no product to buy. I think that if you offered a cleaner distribution, >> >you'd have a viable product. It works for Redhat linux.... >> >ActiveState Perl, Tcl ect. Other companies offer similar Unix-like >> >products, but cygwin is better. :) >> >> If you mean a product as in a $30 CD, then that's not available. >> >> We do have a product, however. It just costs $$$ I just got off of a >> phone call with a potential customer, in fact. >> >> If you mean a product as in a product for which you can send "ssh doesn't >> work" type bugs, then that is not available. The product is >> geared towards >> the development environment. So, gcc and gdb are supported. bash is not. >> ssh is not. >> >> We will sell support for more than just gcc and gdb but we don't have >> standard pricing for that yet. It requires some negotiation. >> Since Red Hat >> is really not in the business of supporting Windows applications, we have >> to be very careful in our Cygwin support deals. Obviously Cygwin is >> not the core focus of Red Hat. >> >> >( Would someone at Redhat please copy this to Rebecca >> Ward AT redhat. I can't find >> >her email, I doubt she reads the list.) >> >> rward at redhat dot com is her address. If you are not getting >> responses from Red Hat sales, please send me private email and I'll try >> get that resolved. >> >> cgf >> >> -- >> 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/ >> >> > > >-- >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/ -- 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/