From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] cmake 3.12.0
Date: Thu, 26 Jul 2018 06:00:00 -0000 [thread overview]
Message-ID: <6bdcf443-2221-7c0e-887b-5bc4d82b559e@gmail.com> (raw)
In-Reply-To: <DM5PR22MB06845DE680D557E91781CB77A72B0@DM5PR22MB0684.namprd22.prod.outlook.com>
Am 26.07.2018 um 02:50 schrieb Tony Kelman:
>> No, all I'm saying that there's a protocol for that. The maintainer is
>> supposed to monitor this list
>
> I do read the mailing list, but don't write to it very often - composing a
> plain-text email is overly complicated with the mobile email clients I use
> most of the time, and I was traveling this past week.
Noted, thanks for the feedback.
> One of the main reasons I haven't put in the effort to update the cmake
> package is that recent versions of cmake have new dependencies which it
> vendors by default, which is not the way distros such as cygwin prefer to
> build things. For a cygwin packaging build of cmake (as with other tools),
> the "right way" is presumably to use system versions of all library
> dependencies. This would require an ITP on at least libuv, and any other
> new dependencies of cmake that the latest version has but 3.6 didn't.
> This might include rhash and json-cpp (looking at how msys2 has updated
> their packaging of cmake over time), but I'm not positive.
In general is better to have a separate package for any dependency;
it make much simpler to maintain all.
I am trying to build and pack libuv.
If I find no problem I will ITP it.
> If Ivan is willing to package and maintain libuv and any other new cmake
> dependencies so they can be de-vendored, I'm fine with him adopting cmake.
> For his own sake, I'd recommend doing a better job than I did of tracking
> down any test failures and pursuing upstreaming the cygwin patches. Many of
> those originate from Yaakov, and there is some past discussion on the list
> about a few of them. Those patches are kind of a pain to rebase with each
> new version, so working to upstream them will save time over the long run.
Can you manage a co-maintainership and guide him on the effort ?
> I haven't reviewed what Ivan has changed in the packaging, patches, etc.
> So heavy cygwin users of cmake, particularly packagers of other cmake-built
> programs and libraries, should carefully test out the new builds.
Noted.
>
> -Tony
Regards
Marco
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2018-07-26 6:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 14:16 Ivan Shynkarenka
2018-07-24 14:18 ` Ivan Shynkarenka
2018-07-24 14:48 ` Marco Atzeri
2018-07-24 14:47 ` Takashi Yano
2018-07-24 19:01 ` Achim Gratz
2018-07-24 20:05 ` cyg Simple
2018-07-24 20:50 ` Achim Gratz
2018-07-24 20:56 ` Ivan Shynkarenka
2018-07-25 6:44 ` Marco Atzeri
2018-07-26 0:50 ` Tony Kelman
2018-07-26 6:00 ` Marco Atzeri [this message]
2018-07-26 7:07 ` Marco Atzeri
2018-07-26 9:28 ` Ivan Shynkarenka
2018-07-26 19:05 ` Tony Kelman
2018-07-26 18:41 ` Achim Gratz
2018-07-26 19:33 ` 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=6bdcf443-2221-7c0e-887b-5bc4d82b559e@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).