DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 4A88Ne1U2671052
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=tawGAPZr
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 95CB93858D37
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1731054218;
	bh=p0WItFI8xuXPpreh0/loU8tEqi21nZ5vJi0vnTQwtgQ=;
	h=To:Subject:Date:References:List-Id:List-Unsubscribe:List-Archive:
	List-Post:List-Help:List-Subscribe:From:Reply-To:From;
	b=tawGAPZr6nn2fbi7ACH0Ap7JN56vF1+xHxY/qJl+ELU2Ihd11iDUtvZMT0PMAG1eB
	MFO+X+U9bZ7N92QZgEKcQlG5PLsmeaZRQrnAYwjOVdw6S5o0BMt+j7QS3DjSYT2pAi
	hm6a0V72L7p9Euj06llAiivHTrkqNfjWzDDkyt64=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org ABBE93858CDB
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org ABBE93858CDB
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1731054196; cv=none;
	b=o4IYo6R/GZHe3wJTA3DcCM5zoOtpmNBGCxC7fReuEibVMxrrWzF0MLo+6/LoHfCSX9lsvFQB/C2DEQtnH2e/7LxmF4Ae/VFjReUBwOJiFGwtMompjowY79698kX6GSAc3gYcguUjAcoKV1nlMUYGDkResWIO7tCC4V8t7TDBp2Y=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1731054196; c=relaxed/simple;
	bh=LGkQXoe5OBcy6346BaTcb8bo0164tvgXXD9TVC7FiLk=;
	h=To:From:Subject:Date:Message-ID:Mime-Version;
	b=MMncOkT/daCLv9yUypCcEv/VsfsQ/8V17N9IyJwBvO9T8iXBt6twbtAv9woG3ADDLQPQDBIfyD8EATlac1dWtRHDgphJLEF5OXuXALyI+plyLWacq2W0NJaZ4ZdL0ghwAHE39ER86rrqzDDN46FPXU8leIjI3eCSj1tUsdHwTSQ=
ARC-Authentication-Results:	i=1; server2.sourceware.org
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
Subject:	Re: cygport upload seems to ignore SSH_KEY
Date:	Fri, 08 Nov 2024 03:23:04 -0500
Message-ID:	<adirijda43mr6clnekftt46stnjc9v9eoo@4ax.com>
References:	<8d85bde3-8ea8-4635-8547-9846315243cf AT kircheis DOT it>
	<7704ca4f-00ba-41b8-897c-7558d846ec18 AT SystematicSW DOT ab DOT ca>
	<nlvjij9vha7u1j71seri65tfg21o7ua3im AT 4ax DOT com>
	<1fe1c4ea-83bd-4fe8-9daf-496ff6ec2c69 AT SystematicSW DOT ab DOT ca>
	<6d211145-71a2-47d5-83ac-e7a3330e30ce AT kircheis DOT it>
Mime-Version:	1.0
X-Newsreader:	Forte Agent 4.2/32.1118
X-Archive:	encrypt
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Andrew Schulman via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Andrew Schulman <schulman DOT andrew AT epa DOT gov>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

> >> I haven't used cygport up in a long time - I use git push now, and let 
> >> scallywag build the packages
> 
> Is this workflow described somewhere?
> It sounds interesting.

Yes!

Git repositories for Cygwin packaging: https://cygwin.com/packaging/repos.html

Once you push your .cygport file up to the package's Cygwin git repo, the
package build service will try to build it:
https://cygwin.com/packaging/build.html


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -