This is the mail archive of the cygwin 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: [OT] polite response to not so polite response - Andrew...


Andrew:

>OK, HE'S RIGHT!
Thank you.

>And here comes Barry, posting for the first time ever, and he is showing us
a thing or two!
Thank you, again.  
Actually, the cygwin manual details the process of executing Windows and DOS
commandline tools
(rar is only one example) from a cygwin script. 
If there is a problem with the cygwin unzip, I'm sure that the maintainers
of cygwin will work 
on it without anyone else making a comment.  I was merely attempting to
provide a solution for
the user with a ZIP-SFX problem on a Windows computer that runs cygwin.
Since I am not a 
cygwin "insider", I can look at the problem as a Windows user who also uses
cygwin, but is 
capable of seeing and expressing a solution beyond the domain of cygwin,
that is actually
discussed in the cygwin manual.

Oh...
> ... posting for the first time ever...
No.  When I first started using cygwin, I might have asked a question or two
on the list...
but I don't remember ever having a problem with cygwin.  
Yes, I have been away from the list for years, and I did just join with this
email address,
but I always search the list archives for guidance, and have rarely required
assistance with
cygwin.
Yes, this is the first time that I have ever offered assistance, because (as
the cygwin experts
on-list explained) the problem is not due to cygwin.  I still believe that
the file size, and 
the specs of the ZIP format are to blame, but that doesn't help the user fix
their problem. It 
just sends the user away who is reaching out with a problem, without
providing any direction 
that the user might not have thought of.  I suggested a Windows alternative,
and others on the
list were correct (and not helpful) to point out that RAR, which _does_ run
on EVERY computer
that runs cygwin is not compatible with the cygwin.dll.     
If cygwin is not to blame, then maybe you should provide questions for the
user with the problem
to think about (or solve their problem with Windows solutions that will work
on their computer), 
or direct them so that they can approach another support avenue.  That way
you're still "off the 
hook", but you've pointed a user looking for help in another direction.

Peace,

Barry Smith
-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of
Andrew Schulman
Sent: Wednesday, September 24, 2008 5:58 AM
To: cygwin@cygwin.com
Subject: Re: [OT] polite response to polite response - Brian...

> I was merely pointing out (subtly and repetitively) that cygwin is an 
> application layer on top of Windows.

WOW!  Are you sure?  Wait a minute, let me check this out...

OK, HE'S RIGHT!  Christopher and Corinna, can we please bring this guy on as
some kind of paid consultant?  I think you might need his help.  I mean,
with all of us posting on this list for so many years, and developing Cygwin
and creating packages for it and all, none of us ever figured this out!  And
here comes Barry, posting for the first time ever, and he is showing us a
thing or two!


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


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