From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17375 invoked by alias); 30 Jun 2010 18:01:33 -0000 Received: (qmail 17263 invoked by uid 22791); 30 Jun 2010 18:01:31 -0000 X-Spam-Check-By: sourceware.org Received: from pool-173-76-48-4.bstnma.east.verizon.net (HELO cgf.cx) (173.76.48.4) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Wed, 30 Jun 2010 18:01:27 +0000 Received: from ednor.cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 8289613C061 for ; Wed, 30 Jun 2010 14:01:25 -0400 (EDT) Received: by ednor.cgf.cx (Postfix, from userid 201) id 7B0152B352; Wed, 30 Jun 2010 14:01:25 -0400 (EDT) Date: Wed, 30 Jun 2010 18:01:00 -0000 From: Christopher Faylor To: cygwin-xfree@cygwin.com Subject: Re: RE: startxwin/XWin won't start properly Message-ID: <20100630180125.GA5400@ednor.casa.cgf.cx> Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com References: <270AA78168E41541833C52448F4F34AD2373AF6A@VHAISHMSGJ2.vha.med.va.gov> <4C2B6CC5.1040603@ece.cmu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C2B6CC5.1040603@ece.cmu.edu> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2010-06/txt/msg00074.txt.bz2 On Wed, Jun 30, 2010 at 06:11:49PM +0200, Ryan Johnson wrote: >> >> What Mike and I want is actually pretty reasonable. We want to be able >> to preserve the work we do in picking the wheat from the chaff (from our >> point of view) to avoid having our coworkers or ourselves duplicate that >> work, whether they understand Unix or not (I'm sorry I brought it up! >> It is largely irrelevant.). It seems simple--at some point the Setup >> program knows what was selected. It just needs to save it out and be >> able to read it back in. >> >vote +1 > >I've also had this need many times. Most recently, the update to the >latest cygwin dll, which the instructions specifically said should be a >clean install rather than an in-place upgrade. Sheesh. The instructions did *not* say that a clean install was needed. We tried hard to make sure that wasn't necessary in fact. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/