X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	q=dns; s=default; b=M+eAxllXWoT3OEMJNS3VYFQy8vhrBE1W0lHxvTFuAZe
	IfE8n+2q8aA1kvxApp4IhNnTvkqkBye1Anff4oztsKRex5OGmrfBYVFsgsoXaljs
	IMYzNV8YskkiTyPh/GlL/T7UhkgulaN+Sgpiu73iMGtsQiY8LtkwkPcm/VC9EDG0
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	s=default; bh=aQmngGK71HEDDBWig1aTc0psMmw=; b=RiaD7nREd7boBKCUf
	rJTlfsADhfDwYbwZqdCE/gSbVZ2zRRw4aX2FF4tKlVgT/L2I3l9JZ8FNcuIxPTFZ
	oR0ibNHZs2ffWrizrR2SXTNqIQ/8uUl6cZYHwn1KLpgltn1OQZzQ5t3vogPRuMsn
	KoT/tf0FEzNWItjEMhTA0wVukE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
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:	<CAMCbSMrMiAkUALo4XDNXK1agVMJt4vacLUo=v6dYJ3H7A4MsWQ AT mail DOT gmail DOT com>
In-Reply-To:	<CAMCbSMrMiAkUALo4XDNXK1agVMJt4vacLUo=v6dYJ3H7A4MsWQ@mail.gmail.com>
From:	Adam Dinwoodie <adam AT dinwoodie DOT org>
Date:	Fri, 28 Jun 2019 14:01:45 +0100
Message-ID:	<CA+kUOak20hAjGbZDuOuMHHHjDDCoTuSbtOMjpBq72zw7e8WmTQ@mail.gmail.com>
Subject:	Re: Question about packaging and cygport
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id x5SD2uNJ025011

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 – or even if – 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

- Raw text -