git repositories for cygwin packaging - please test

[Jon Turney]

On 04/08/2019 21:08, Jon Turney wrote:
> To remedy this lack, using the same ssh key you use for sftp package 
> upload, package maintainers can now also push to git repositories, like so:

Package maintainers may have noticed that the output from pushing to 
these git repositories now includes a line like:

"remote: scallywag: build nnn queued"

This is a *prototype* of a system to automatically build the packages, 
where the results appear (some time later) at [1] (URL subject to change)

[1] https://cygwin.com/cgi-bin2/jobs.cgi

Currently, many packages will fail to build correctly due to:

(i) missing or insufficient 'BUILD_REQUIRES',
(ii) missing prerequisites implied by an 'inherit' (a bug in this system),
(iii) resource limits imposed by AppVeyor's free service which is used 
to perform the actual builds, or
(iv) other bugs in this system.

At this stage, this is only probably useful for verifying that 
BUILD_REQUIRES is correct.

(Note that a successful build doesn't always mean that you have 
reproduced your build: You'll need to check the configuration step 
output and/or dependencies of the produced packages are the same. 
Consider explicitly enabling the functionality you are expecting in the 
options to the configure script , if it supports that (e.g. 
CYGCONF_ARGS, etc.), to avoid it potentially silently turning off in 
future, if it's requirements change)

To allow experimentation without messing up the version history 
unnecessarily:

- All package repositories allow the maintainer(s) to create, push, 
rewind and delete a branch named 'playground'.

- An additional package repository called 'playground' exists, that all 
maintainers can do anything to.