From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: change in behavior of make from 3.80 to 3.81
Date: Wed, 16 Aug 2006 20:41:00 -0000 [thread overview]
Message-ID: <ebvvrc$mqd$1@sea.gmane.org> (raw)
In-Reply-To: <20060816200428.GA27256@calimero.vinschen.de>
Corinna Vinschen wrote:
> On Aug 16 14:17, Bob Rossi wrote:
>>>> I think your solution is well stated. Does anyone know who was
>>>> maintaining the old patch to make, so that a discussion with that
>>>> person could be made more substantial on a technical level?
>>> And ^^^this^^^ is a perfect example of why this discussion is so
>>> frustrating.
>>>
>>> Does someone *really* have to tell you who was "maintaining the old
>>> patch"? If you really need to be told this then you really don't have
>>> the right to an opinion on this subject at all since you clearly haven't
>>> been paying any attention.
>> I think you are all to knowledgeable about cygwin and should step back
>> and think about people that use Cygwin as a black box and understand
>> absolutely nothing about it or it's development process. The frustration
>
> This has nothing to do with Cygwin's development process. Cygwin is a
> POSIX environment after all. It's one of if's design targets to get rid
> of the DOS paths. People using Cygwin with DOS paths are using Cygwin
> for something it was not designed for. This whole complaint comes up
> because people are using Cygwin in a non-standard way. I'm wondering
> why nobody complains that Linux doesn't understand drive letters.
Well, the obvious answer is because Linux doesn't *have* drive letters. ;-)
>> you are expressing is understandable to me. However, with a little
>> managerial effort on your part, you could use your knowledge (if you so
>> choose) to help the rest of us organize a productive way to develop a
>> patch to the upstream make. I thought Corinna spoke very well on this
>> matter, and is why I even bothered responding to this list.
>
> Maybe you got me wrong. I have a very strange feeling about getting
> told my point of view would be right, while in the same sentence you're
> kicking cgf's ass. Just for the records: My design goals for Cygwin
> are that it works fine as a POSIX environment, not that it works fine
> to run DOS tools. That's a nice side-effect at best.
Just to jump over to the other side here for a second... I assume you
don't intend to ever make it /impossible/ to run DOS tools on Cygwin?
That IMO *would* be unacceptable and unrealistic. But, of course, that's
what interface tools - like cygpath - are for. IOW, the ability to offer
a "pure POSIX" environment is good, as long as it does not preclude any
communication whatsoever (no matter how clunky) with Windows.
I think I've made my position on the 'make' decision known; I have
absolutely no problems with it, and I support it. Just as long as I can
still pipe between DOS and Cygwin applications(*), share file systems,
and have something like 'cygpath', Cygwin can (and should) be as
POSIX-like as it wants. :-)
(* Interix is even worse, here! For pipes to work, you have to call all
DOS programs from an Interix wrapper program! ...but even that is
acceptable because it still *can* be done.)
--
Matthew
vIMprove your life! Now on version 7!
next prev parent reply other threads:[~2006-08-16 20:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6.2.3.4.2.20060815151104.0b40e260@pop.nycap.rr.com>
[not found] ` <01b901c6c116$21259430$a501a8c0@CAM.ARTIMI.COM>
[not found] ` <6.2.3.4.2.20060816091525.0ab90af0@pop.nycap.rr.com>
[not found] ` <20060816144110.GX20467@calimero.vinschen.de>
[not found] ` <20060816174406.GA7538@brasko.net>
[not found] ` <20060816180659.GA5064@trixie.casa.cgf.cx>
2006-08-16 18:21 ` mwoehlke
2006-08-16 18:45 ` Christopher Faylor
2006-08-16 19:19 ` mwoehlke
[not found] ` <20060816181709.GB7538@brasko.net>
[not found] ` <20060816200428.GA27256@calimero.vinschen.de>
2006-08-16 20:41 ` mwoehlke [this message]
2006-08-16 20:46 ` Christopher Faylor
2006-08-16 21:32 ` mwoehlke
2006-08-16 21:37 ` Christopher Faylor
2006-08-16 21:42 ` mwoehlke
2006-08-16 21:17 ` Corinna Vinschen
2006-08-16 21:48 ` Douglas Goodall
2006-08-16 22:17 ` Christopher Faylor
2006-08-16 22:28 ` Douglas Goodall
2006-08-16 22:38 ` Christopher Faylor
2006-08-17 7:12 ` Corinna Vinschen
2006-08-17 14:34 ` Christopher Faylor
2006-08-17 23:37 ` George
2006-08-28 0:07 ` Joe Smith
[not found] ` <6.2.3.4.2.20060816111421.0b446b60@pop.nycap.rr.com>
[not found] ` <20060816155054.GY20467@calimero.vinschen.de>
[not found] ` <Pine.GSO.4.63.0608161418370.9095@access1.cims.nyu.edu>
[not found] ` <6.2.3.4.2.20060816144036.09695af0@pop.nycap.rr.com>
[not found] ` <Pine.GSO.4.63.0608161543520.14156@access1.cims.nyu.edu>
[not found] ` <E1GDdoK-0002Ml-Re@fencepost.gnu.org>
[not found] ` <Pine.GSO.4.63.0608170950440.14156@access1.cims.nyu.edu>
[not found] ` <Pine.GSO.4.63.0608171010080.14156@access1.cims.nyu.edu>
2006-08-17 15:17 ` mwoehlke
2006-08-17 15:33 ` Igor Peshansky
2006-08-17 16:12 ` mwoehlke
2006-08-17 16:17 ` Dave Korn
2006-08-17 16:38 ` Igor Peshansky
[not found] <17632.65094.528377.623813@segfault.lan>
[not found] ` <009a01c6bfff$934e8480$a501a8c0@CAM.ARTIMI.COM>
[not found] ` <17633.5335.965102.80534@segfault.lan>
[not found] ` <44E1FF26.6040707@netacquire.com>
[not found] ` <17634.17135.395022.903332@segfault.lan>
[not found] ` <ebtj8t$eh9$1@sea.gmane.org>
[not found] ` <20060815230423.GC6297@trixie.casa.cgf.cx>
2006-08-15 23:57 ` mwoehlke
2006-08-16 0:51 ` Christopher Faylor
[not found] <44E0F683.3030203@netacquire.com>
2006-08-15 1:18 ` Gary R. Van Sickle
2006-08-15 1:24 ` Dave Korn
2006-08-15 1:31 ` Gary R. Van Sickle
2006-08-15 2:36 ` Dave Korn
2006-08-15 2:50 ` Igor Peshansky
2006-08-15 4:05 ` Gary R. Van Sickle
2006-08-15 8:51 ` Dave Korn
2006-08-15 13:30 ` Igor Peshansky
2006-08-15 1:29 ` Christopher Faylor
2006-08-15 1:35 ` Gary R. Van Sickle
2006-08-15 2:41 ` Dave Korn
2006-08-15 4:15 ` Gary R. Van Sickle
2006-08-15 8:55 ` Dave Korn
2006-08-15 13:29 ` Igor Peshansky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ebvvrc$mqd$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).