Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020403114503.0263aa60@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Wed, 03 Apr 2002 12:00:50 -0500
To: Alan Dobkin <Alan AT ADobkin DOT Net>, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: ncftp current release won't run - missing CYGREADLINE5.DLL
In-Reply-To: <2570919046.1017833940@[192.168.70.5]>
References: <20020403160028 DOT GL4053 AT redhat DOT com>
 <20020403160028 DOT GL4053 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:39 AM 4/3/2002, Alan Dobkin wrote:
>--On Wednesday, April 03, 2002 11:00 AM -0500 Christopher Faylor
><cygwin AT cygwin DOT com> wrote:
>
> > On Wed, Apr 03, 2002 at 07:48:29AM -0800, Gord Wait wrote:
> >> It turns out, no you can't just re run setup.exe on an already
> >> installed cygwin and expect it to work.  It might delete a dll 
> >> or two for you due to an install bug.
> > 
> > That is just not true.  Please don't spread misinformation.
>
>In my experience, Gord's first statement above *is* true.  Even 
>though the current setup has been fixed so this problem does 
>not happen with new installations, it does not go back and fix 
>the problem for people who used the old setup.  The user must 
>manually find the missing DLLs, or use a command like this:
>
>cd / && ls `zcat /etc/setup/*.gz | grep -v etc/postinstall` >/dev/null
>
>Then setup must be forced to reinstall the appropriate packages; 
>it does not automatically recognize that they need to be updated.
>
>Incidentally, IMO Gord's solution to completely reinstall Cygwin 
>from scratch is overkill.  Finding the missing DLLs and having 
>setup reinstall them is much easier and should be just as clean.


As with any problem, there are multiple ways of fixing it.   Gord's 
statement implies a specific case, which was a problem in the past, is
still a problem in general.  In that context, it is wrong, as Chris 
points out.  It will mislead and confuse most who happen to take the 
time to research a similar problem they might be having.  For 
those that don't, won't, or can't use the fix that the current setup 
provides, then obviously your prescribed solution is valid and works.  
The general audience of this list will likely find it less appealing 
though since it requires more than the typical "point and click" effort.

In any case, there is no outstanding issue here.  It's all been addressed
before and the solution exists.  It doesn't need to be invented.  Unless a 
serious problem arises again with the previously prescribed approach in 
the FAQ, there's no benefit to this list in continuing the discussion of
solutions to this issue.  I may be wrong but I believe that was the point
that Chris was trying to get across.





Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/