GCL and dependencies on cygwin

[Brian Inglis]

On 2025-03-10 05:42, Camm Maguire wrote:
> Greetings, and thank you so much for your helpful reply!
> Brian Inglis via Cygwin wrote:
>> On 2025-03-09 08:16, Camm Maguire via Cygwin wrote:

>> In general, these topics are best discussed on cygwin-apps, to which all
>> packagers, maintainers, and contributors are expected to subscribe.

> Thanks so much -- I will carry this conversation there.  But in general
> the first step is the same, i.e. to upload sources to a pubic area and
> get approval from an existing maintainer?

First get the package building and testing cleanly using:

	$ cygport gcl.cygport get all check

You can use clisp as an example for what info is expected:

	https://cygwin.com/packages/summary/clisp-src.html

although more recent cygports better show current required variable definitions 
and preferred "spellings"

Then create a local git repo gcl containing the cygport (and any patches or 
other included sources);
checkout your sources on a playground branch;
and force push that branch to Cygwin's package playground repo:

	https://cygwin.com/git/cygwin-packages/playground.git

which should start running a Cygwin Scallywag CI process under GitHub Actions:

	https://cygwin.com/cgi-bin2/jobs.cgi

which will get your package sources into the Cygwin playground package repo, and 
provide a PoC of your package build and test.

Subscribe to and create an email addressed to cygwin-apps with subject like:

	Subject: [ITP] gcl 2.6.14 - GNU Common Lisp

ITP == Intent To Package (ITA == Intent To Adopt [existing orphaned])

and provide links to the project upstream homepage, state its current 
availability across Linux and other Unix systems, with a Repology link:

	https://repology.org/project/gcl/versions

and provide links to the sources in the playground repo, and the relevant 
Scallywag arch build job log, from the GitHub Actions job.

You will get feedback and/or further instructions about suggested changes; 
acceptance; providing an SSH key for repo, upload, and announce access [and 
request for BSD-2-Clause contributor's agreement?]

You can see what others' ITPs look like from our mailing list Public Inbox 
instances under the Sourceware domain, which hosts Cygwin (and many other major 
open source projects):

	https://inbox.sourceware.org/cygwin-apps/?q=%5BITP%5D

[If you have policy/philosophical objections to using GitHub Actions, an 
alternative Appveyor instance is still available, which we all used to use: 
search the docs and mailing list for details!]

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry