From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Trouble trying to compile apache2
Date: Sun, 20 Feb 2022 16:34:36 +0000 [thread overview]
Message-ID: <20220220163436.x24jwpu44b2vt345@lucy.dinwoodie.org> (raw)
In-Reply-To: <b5525bba-e2e9-3e82-3cea-5a1721adb261@dronecode.org.uk>
On Thu, Feb 17, 2022 at 03:37:00PM +0000, Jon Turney wrote:
> On 16/02/2022 10:40, Adam Dinwoodie wrote:
> > <snip>
> > Inevitably a bunch of other maintainers will have their own way of doing
> > things; I think Scallywag is the closest thing we have to a common CI/CD
> > setup. But hopefully some of this might give you pointers to CI/CD
> > tools that require minimal setup and won't even cost you time on your
> > own build servers. Or, at the very least, ideas about what you'll need
> > to do for your own automation.
>
> I have no great attachment to the current system. It saves me a bit of time
> maintaining my packages, and might be of some benefit to others.
>
> Long-term, the ambition would be to stop maintainers uploading locally built
> packages, because that's not a good idea.
>
> If you have ideas on improvements which could benefit all package
> maintainers (or even everyone who wants to try to build cygwin packages),
> and would like to work on that, let me know and I'll sort out access to
> sourceware for you.
I'm definitely interested! This sounds like the sort of thing I'd think
is a fun time. I don't think I can commit to doing anything on any
particular time frame, but I think I'd enjoy working on that sort of
infrastructure project and I'd be very glad to contribute.
next prev parent reply other threads:[~2022-02-20 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 22:25 Scott Wood
2022-02-15 7:17 ` Russell VT
2022-02-15 12:39 ` Adam Dinwoodie
2022-02-15 12:50 ` Russell VT
2022-02-16 10:40 ` Adam Dinwoodie
[not found] ` <b5525bba-e2e9-3e82-3cea-5a1721adb261@dronecode.org.uk>
2022-02-20 16:34 ` Adam Dinwoodie [this message]
2022-02-17 15:35 ` Jon Turney
2022-02-17 15:50 ` Scott Wood
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=20220220163436.x24jwpu44b2vt345@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin@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).