From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag CI
Date: Wed, 22 Sep 2021 22:29:32 -0600 [thread overview]
Message-ID: <3cfa0754-1e48-2864-7fa3-9b89e3987314@SystematicSw.ab.ca> (raw)
In-Reply-To: <06c901d7b017$201b10a0$605131e0$@pdinc.us>
On 2021-09-22 19:05, Jason Pyeron wrote:
> On Wednesday, September 22, 2021 8:44 PM, Brian Inglis wrote:
>> Your push should do a lazy create of the git repo, and start the
>> scallywag CI job on Github actions.
> In my case, the build requires much older versions of Cygwin to build at the moment. Would this be hopeless for now?
>> Don't forget to commit any patches or external files used, and specify
>> all packages required to build, create docs, and run tests in
> Are the source files downloaded via URL, those are not part of the commits.
Besides some git clones to setup and operate the scallywag environment,
Cygwin Setup runs to install the base, cygport, and dependent packages;
>> BUILD_REQUIRES, to be installed before configure, make, and make check
>> are run.
then the package cygport BUILD_REQUIRES packages, before running cygport
download all check with the pushed sources in the current directory,
downloading and if necessary untaring all SRC_URI and PATCH_URI files
under the origsrc directory.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-09-23 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 1:05 Jason Pyeron
2021-09-23 4:29 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cfa0754-1e48-2864-7fa3-9b89e3987314@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).