From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin@cygwin.com
Subject: Re: trouble posting to cygwin-apps
Date: Thu, 07 Oct 2010 12:54:00 -0000 [thread overview]
Message-ID: <4CADC30B.9060505@kitware.com> (raw)
In-Reply-To: <1286432454.5420.49.camel@YAAKOV04>
On 10/7/2010 2:20 AM, Yaakov (Cygwin/X) wrote:
> On Tue, 2010-10-05 at 18:13 -0400, Bill Hoffman wrote:
>> Really this belongs on the CMake dev list.
>
> In so much as this affects a Cygwin packages, it is perfectly on topic
> here.
>
>> The new release I just posted is not really a new release of CMake, but
>> it is a new release for cygwin. The current cmake that comes with
>> cygwin is 2.6.4 (very old). The one I just uploaded was 2.8.2 (still
>> old but much newer.) It has no changes at all.
>
> How exactly is 2.8.2 old when it is the latest official release?
>
>> We are currently working on 2.8.3, it has some of the patches you want,
>> but not all. However, please work with me on the cmake dev list to come
>> up with a solution that won't break all of the projects I support (VTK,
>> ITK, and several others).
>
> That may be the long term solution, but right now we need a working
> cmake, and your 2.8.2-1 isn't it. You want WIN32 defined on Cygwin, but
> *we* do not. As so far as the Cygwin distribution is concerned,
> shouldn't the views of those who make the distribution take priority?
>
>> I do not want to create a cygwin release that does not match the
>> upstream CMake.
>
> Unfortunately we need you to do exactly that until upstream has been
> fixed.
>
So, I thought that I was the cmake maintainer for cygwin? So, really I
don't "need" to do anything. I really don't want two version out there.
If someone builds CMake from source and it behaves totally different
than the one that comes with cygwin, that IMO is a very bad thing, and
will cause lots of confusion. And seriously we are working on exactly
what you want, and CMake has been like this for 10 years now, I would
think you could be a bit more patient and give me some more time to come
up with the correct fix.
-Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-10-07 12:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:33 Bill Hoffman
2010-10-05 8:07 ` Corinna Vinschen
2010-10-05 12:29 ` Bill Hoffman
2010-10-05 15:32 ` Corinna Vinschen
2010-10-05 20:46 ` Charles Wilson
2010-10-05 21:29 ` Bill Hoffman
2010-10-05 21:47 ` Marco Atzeri
2010-10-05 21:51 ` Yaakov (Cygwin/X)
2010-10-05 22:13 ` Bill Hoffman
2010-10-07 6:21 ` Yaakov (Cygwin/X)
2010-10-07 12:54 ` Bill Hoffman [this message]
2010-10-05 22:31 ` OpenCV: (Re: trouble posting to cygwin-apps) Yaakov (Cygwin/X)
2010-10-06 3:34 ` Charles Wilson
2010-10-07 21:45 ` trouble posting to cygwin-apps Christopher Faylor
2010-10-07 21:57 Gregg Levine
2010-10-07 22:16 ` Christopher Faylor
2010-10-08 13:05 ` Bill Hoffman
2010-10-08 6:20 SZABÓ Gergely
2010-10-08 13:52 ` Eric Blake
2010-10-08 15:41 ` Christopher Faylor
2010-10-08 19:27 ` Kenneth Wolcott
2010-10-11 8:01 ` Csaba Raduly
2010-10-11 8:12 ` SZABO Gergely
2010-10-08 14:20 SZABO Gergely
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=4CADC30B.9060505@kitware.com \
--to=bill.hoffman@kitware.com \
--cc=cygwin@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).