This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] cygcheck: warn about empty path-components


On Fri, Oct 08, 2004 at 01:42:05AM +0200, Bas van Gompel wrote:
>: > :  Why are we bothering with this?
>: >
>: > If I may attempt to answer this one... Many people may not know of
>: > this usage, yet may have their windows path ending on a ';'.
>:
>:   I'm sure the same thing is true on UNIX and yet it has survived for
>:  years without a unicheck program informing people of this fact.
>
>There are no windows paths in UNIX, and there is no unicheck program
>for any purpose. Does this mean cygcheck should be removed?

We're talking about paths, not "Windows paths".

Cygcheck was invented as a bug reporting adjunct so that we wouldn't
have to keep asking people to send us the output of the mount command
and the which command and the env command, etc.  There are similar
programs on linux.  The name of the one that Red Hat uses escapes me
but, in Red Hat tech support, it was standard procedure to ask people to
include output from this program in their bug reports.

Of course, if someone can use cygcheck to diagnose their own problems
then, that's great.  I don't see any reason to alarm someone with a
warning about a minor issue like an empty path component when it
is not an uncommon idiom, though.

>What are you planning to do? Will you revert this patch, reject the
>next patch and leave things as they are, or consider it when it's
>submitted?

I'm leaning to reverting the patch unless you can point me to a
preponderance of email messages in the cygwin list which illustrate
that this has been a common problem crying out for a warning.  Maybe
I just missed something.

If you are interested in adding real improvements to cygcheck, I'd
suggest something to ensure that the permissions on system directories
and files are sane, and maybe even a method to correct problems in that
area.  That seems to be one of the biggest complaints in the mailing
list.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]