public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] cmake-3.18.0-1 and related packages
Date: Fri, 17 Jul 2020 23:13:55 +0200	[thread overview]
Message-ID: <7c101cc2-7e2b-38dd-fe36-b06023efe08b@gmail.com> (raw)
In-Reply-To: <20200718051428.2298.50F79699@gmail.com>

On 17.07.2020 22:14, Lemures Lemniscati via Cygwin-apps wrote:
> Hi!
> 
> I suggest an update to CMake v3.18.0 (Date: Wed Jul 15 07:19:20 2020 -0400).
> https://github.com/Kitware/CMake/tree/v3.18.0
> 
> I'm not at all familiar with CMake, which is a very large system.
> And, though I don't mind being an additional maintainer for cmake,
> I guess it's difficult for me to maintain cmake packages just by myself.

cmake is a bit of pain, I can agree

>> Current maintainers are: https://cygwin.com/cygwin-pkg-maint
>> cmake                                        Tony Kelman/Marco Atzeri
> 

technically as I am still here, cmake is not orphan


> New cygport and patch files are placed
> to https://github.com/cygwin-lem/cmake-cygport/tree/n_3.18.0-1d
> (I can't find any git repository for cmake.cygport).

all mine are together at

https://github.com/matzeri/cygwin-pkg


> New test package files are placed here:
> https://app.box.com/s/8q5mpv4kv080jxsyc5tbongrerwfzbuz/folder/118159586901

I will give a view

> 
> cmake-3.18.0-1
> cmake-doc-3.18.0-1
> cmake-gui-3.18.0-1
> bash-completion-cmake-3.18.0-1
> emacs-cmake-3.18.0-1
> vim-cmake-3.18.0-1
> 
> There are new additional packages: bash-completion-cmake and vim-cmake-3.18.0-1.
> They contain new files in CMake v3.18.0 and not in earlier versions
> 
> --
> Lem
> 

I have cmake-3.17.3-1 build and already packed, but I am no
really fine with testing

any reason why you need 3.18.0

Regards
Marco

  reply	other threads:[~2020-07-17 21:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 20:14 Lemures Lemniscati
2020-07-17 21:13 ` Marco Atzeri [this message]
2020-07-18  1:00   ` Lemures Lemniscati
2020-07-18  6:12   ` Achim Gratz
2020-07-18  6:29     ` Marco Atzeri
2020-07-18  7:01       ` Achim Gratz
2020-07-18  8:13         ` Achim Gratz
2020-07-18 10:09         ` Lemures Lemniscati
2020-08-07 16:06           ` cmake upstream has merged cygwin patches Lemures Lemniscati
2020-08-07 19:51             ` Marco Atzeri
2020-08-08  0:47               ` Lemures Lemniscati
2020-08-10  8:17                 ` Marco Atzeri
2020-08-10 13:12                   ` Lemures Lemniscati
2020-11-19 22:45           ` cmake-3.19.0-1 and related packages Lemures Lemniscati
2020-11-25 22:11           ` cmake-3.19.1-1 " Lemures Lemniscati
2020-12-17 21:30           ` cmake-3.19.2-1 " Lemures Lemniscati
2021-03-27 15:58             ` Marco Atzeri
2021-03-27 22:02               ` Lemures Lemniscati
2021-03-28  2:45                 ` Lemures Lemniscati
2021-03-28  7:00                   ` Marco Atzeri
2021-03-28  0:12               ` Lemures Lemniscati
2021-03-28  7:02                 ` Marco Atzeri

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=7c101cc2-7e2b-38dd-fe36-b06023efe08b@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin-apps@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).