Re: setup.exe timestamp 1108087248: mined-2000.10-1: minor glitch

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Fri, Feb 11, 2005 at 06:54:53PM +0000, fergus wrote:
>> What is your *exact* problem?
>
>I visited the Cygwin site www.cygwin.com/setup.exe (as one does) and
>trawled for updates. This was about 12 hours ago. There were none,
>apparently. But I observed that setup.ini stamped ..7248 (just as it is
>now, in fact) had altered since my previous visit, and not in a minor
>way: there was a new provision in the form of mined. I had asked for
><Install> not <Default> and in the usual way of things this would have
>been identified and downloaded and installed. All I had was the new
>setup.ini. I looked at it (a) to see what was new (mined) and (b) what
>was odd or wrong, leading to this failure. All that I observed even
>moderately unexpected was the blank line in the middle of ldesc. I
>closed it, wget'd mined into my local resource, and again used
>setup.exe, using "my" setup.ini and my local resource. The new provision
>was identified and installed.
>I deduced, wrongly, that my editing tweak was what had mended things. I
>later observed (see "More:" at 09.02) that a blank line in ldesc does
>not uniquely characterise mined, and therefore that something else,
>maybe to do with the exact timing of my visit to the mirror, was the
>cause of the glitch.

I think you're not quite getting the point here.

Your original report contained your interpretation of a cause of a problem
without any explanation about the actual problem.

Here, you've gone into TMI mode.

I think your problem can be summarized by saying "When I ran setup.exe
and chose, 'mined' did not get installed and I think it should have."

A succinct description of the problem is all that's required.  If you
have a theory about what's causing the problem that's great too, but
just including the theory without talking about the problem is usually
just going to result in someone asking you to describe the problem.  So,
to cut down on bandwidth a problem report should always try to include a
clear and succinct description of the problem.

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/