From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: Is any chance to update cmake package?
Date: Wed, 18 Jul 2018 13:31:00 -0000 [thread overview]
Message-ID: <CAEhDDbB=-5F9Ss-cOLAdUPQx7VMySfcTLYqcjYDjtZeP0OXwag@mail.gmail.com> (raw)
In-Reply-To: <CAOFWiYZmtq6qjB1+sFGM47U=63qDsZfDH=C_60pMR-QS0nezqA@mail.gmail.com>
Hi Sonic Brown,
On Wed, Jul 18, 2018 at 4:18 AM, Sonic Brown wrote:
> Agreed, any reason why this can't be done?
>
> On Sun, Jun 24, 2018 at 8:07 PM Ivan Shynkarenka <c........@g.....com>
> wrote:
>
>> Hello!
>>
>> Cygwin cmake package is too old with 3.6.2-1 version. Is there any chance
>> to update the package to some recent version?
Please don't top-post on this list. https://cygwin.com/acronyms/#TOFU
Also, please don't quote email addresses in full.
https://cygwin.com/acronyms/#PCYMTNQREAIYR
The reason for cmake not being updated to the latest version is
insufficient amount of round tuits by the cmake maintainer.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
--
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
prev parent reply other threads:[~2018-07-18 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 9:29 Ivan Shynkarenka
2018-07-18 12:42 ` Sonic Brown
2018-07-18 13:31 ` Csaba Raduly [this message]
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='CAEhDDbB=-5F9Ss-cOLAdUPQx7VMySfcTLYqcjYDjtZeP0OXwag@mail.gmail.com' \
--to=rcsaba@gmail.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).