Re: git repositories for cygwin packaging - please test

[Jon Turney <jon.turney@dronecode.org.uk>]

On 30/08/2020 16:46, Jon Turney wrote:
> On 30/08/2020 16:22, Ken Brown wrote:
>> On 8/30/2020 11:00 AM, Jon Turney wrote:
>>> On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
>>>> On 8/23/2020 5:01 PM, Jon Turney wrote:
>>>>>
>>>>> I now have built an (opt-in) system which fetches the packages 
>>>>> built by this into your upload area and triggers calm to process 
>>>>> them, which I'm looking for a volunteer to test.
>>>>
>>>> I'd be willing to give it a try the next time I have something to 
>>>> upload.  I'm actually almost ready for a test release of doxygen. 
>>>> Unfortunately, the 32-bit scallywag build of doxygen consistently 
>>>> fails with an ld crash, even though I can build it locally.  So I 
>>>> can't use it for this test.
>>>>
>>>> How does the opt-in process work?  Is it per package?  Is it easy to 
>>>> opt-out again temporarily?
>>>
>>> We can arrange the details however you like.  A specific package 
>>> might be a good idea for a first try.
>>
>> OK, I've got a test release of ghostscript ready to go.  I've already 
>> tested it on the playground branch, so I know it builds.  If I put 
>> 'SCALLYWAG=deploy' in the cygport and push to master, will that do the 
>> job?
> 
> Sure, I have made things work like that.
> 
> Go ahead when you are ready.

This is now enabled for all maintainers.

To summarize, the following tokens are recognized in the SCALLYWAG 
variable set in the .cygport file:

nobuild: Disables building packages.

notest: Disables running 'cygport test'

deploy: For the master branch, after a successful build, the built 
packages are handed-off to calm, the package uploader.

Note that currently, these packages are built using 'cygport
all-test', and so will always be marked as test.c