From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67194 invoked by alias); 28 Jun 2019 13:02:25 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 67178 invoked by uid 89); 28 Jun 2019 13:02:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=packaging, packaged, cmakecygport, plplot.sf.net X-HELO: mail-vk1-f177.google.com Received: from mail-vk1-f177.google.com (HELO mail-vk1-f177.google.com) (209.85.221.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 28 Jun 2019 13:02:23 +0000 Received: by mail-vk1-f177.google.com with SMTP id 9so1211947vkw.4 for ; Fri, 28 Jun 2019 06:02:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dinwoodie.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=ScgJLpz2OSdvkkXg4bv1IM95OmOyJe+mm923NCS22BE=; b=cfHZLxvJ0umzA7jnjtOOF3CQdShpnHd+S5GNvooUOKE+KcbITuXzCcsvYiPn5Hg/mW ChUq9ewoXgBPzMOecauaggcilkX30ooCtuT6tUqSBbnKNe6QLy2IHbfSEWyYdLvwfPSi NK9kf/h1e/zZmYvyduch2DWNlc2/fDI9169gE= MIME-Version: 1.0 References: In-Reply-To: From: Adam Dinwoodie Date: Fri, 28 Jun 2019 13:02:00 -0000 Message-ID: Subject: Re: Question about packaging and cygport To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00225.txt.bz2 On Fri, 28 Jun 2019 at 11:56, Arjen Markus wrote: > In the context of the PLplot project (plplot.sf.net) we are interested > in the details of how software is packaged for Cygwin, in particular > how CMake is packaged (development of this package is rather fast and > we attempt to keep up with it, so that we can clean up the various > workarounds). > > To better understand the process, we would like to know, how packaging > is arranged - is that via "cygport" files? And if so, what is the > authorative location of these files (notably cmake.cygport)? If some > other method is used, could you enllighten us about the actual > process? Cygport provides a way for maintainers to build packages that are compatible with the Cygwin package distribution tools, so most maintainers use it, but I think there are still a few packages that are maintained without cygport; provided maintainers upload packages that are compatible with the package distribution tools used by the Cygwin project, maintainers are free to use whatever tools they like. In the specific case of cmake, that package does use cygport, but it's not guaranteed that all packages will. The only authoritative source of these files will be the source package downloads you can get through the Cygwin installer, by ticking the "Src?" box in the setup-(x86|x86_64).exe installer. Those are only guaranteed to include the source code itself, but for any package using cygport, you can expect they'll also include the cygport file and any associated files. There's no general repository for the packaging tools and configuration other than that which maintainers have uploaded to provide via the packaging distribution mirrors. Some maintainers will keep their cygport files on GitHub or similar (I do), but that's entirely down to the preferences of the individual maintainer, and I don't know where =E2=80=93 or even if =E2=80=93 the cmake= cygport files are available anywhere else. Adam -- 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