From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31372 invoked by alias); 26 Jul 2018 06:00:38 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 31096 invoked by uid 89); 26 Jul 2018 06:00:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=3.8 required=5.0 tests=BAYES_50,FOREIGN_BODY,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS,TIME_LIMIT_EXCEEDED,UNSUBSCRIBE_BODY autolearn=unavailable version=3.3.2 spammy=EMail, E-Mail, UD:avast.com, wwwavastcom X-HELO: mail-wr1-f54.google.com Received: from mail-wr1-f54.google.com (HELO mail-wr1-f54.google.com) (209.85.221.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Jul 2018 06:00:04 +0000 Received: by mail-wr1-f54.google.com with SMTP id t13-v6so409651wrv.12 for ; Wed, 25 Jul 2018 23:00:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=IcqTRkXgDr27bZWZ7PiZFTDDweYJlrRwyz+q0UppL/s=; b=WiyNuwe1Agi+P+8ZgcyLglsV1XstzE0pDET3gbcNyUn5Y+uNLlGk8FSnxdONFKu/ir fNgtUk7G8TJEBy/rPZqqEK/3hvkfAPvwfBHhjs1AcUn8JOeQn8wNk9nKDCKqf1XVMYm/ VBZtaGwzYxqf+iLNaidZgqa3oKxTvImQIrInJeCOTHD1zQsX44mv5Nf5KliPnaolXez5 1arfhhF2o51UCNuBe6CcN4l+98/AMZHLc+Gcxb74Ko3IsGkHOUztcvtSghOp6F8fx/2P qdagOlyyBN0ENcEwm3oS+zFzx09xmVaEvxXS11FyaMTbhT/fBZV2zoS+LbAD07R83TKx 4k4g== Return-Path: Received: from ?IPv6:::1? (p200300EE63CB23017C0F57EA5D3C5348.dip0.t-ipconnect.de. [2003:ee:63cb:2301:7c0f:57ea:5d3c:5348]) by smtp.gmail.com with ESMTPSA id u18-v6sm715264wrm.80.2018.07.25.23.00.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Jul 2018 23:00:01 -0700 (PDT) Subject: Re: [ITA] cmake 3.12.0 To: cygwin-apps@cygwin.com References: <87h8kobgqc.fsf@Rainer.invalid> <87d0vcbbpn.fsf@Rainer.invalid> <6e0f7d2f-c9a5-bb79-7c8d-161dcf20ec3f@gmail.com> From: Marco Atzeri Message-ID: <6bdcf443-2221-7c0e-887b-5bc4d82b559e@gmail.com> Date: Thu, 26 Jul 2018 06:00:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2018-07/txt/msg00105.txt.bz2 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