public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Trouble trying to compile apache2
Date: Tue, 15 Feb 2022 12:39:41 +0000	[thread overview]
Message-ID: <20220215123941.yxesbunapq3gaxgq@lucy.dinwoodie.org> (raw)
In-Reply-To: <CANV2+nUQrd-wU170JMcN4bji9kzAp6uOGfnaRAQNauWHkLetOQ@mail.gmail.com>

On Mon, Feb 14, 2022 at 11:17:59PM -0800, Russell VT wrote:
> On Mon, Feb 14, 2022 at 2:26 PM Scott Wood <> wrote:
> 
> > I'm trying to compile a current version of apache2 httpd under the cygwin64
> > environment. There is an older version of apache2 compiled in cygwin but
> > it's orphaned and didn't include some of the ssl libs I needed.
> >
> 
> Well, I wouldn't call it "orphaned" ... it's just a few dot revisions
> behind. Both 2.4.29 and 2.4.25 seem to be in the package list, and current
> is 2.4.52 (2021/12/20)

From a formal Cygwin package management perspective, the package is
orphaned.  That is, the page at https://cygwin.com/cygwin-pkg-maint
lists the package as "ORPHANED", which means nobody is currently taking
specific responsibility for answering questions about the package or
providing updates in future.

That obviously means that volunteers to maintain the package would
almost certainly be gladly received.  I've not looked at how much work
is required to maintain this package, but as a maintainer for some other
packages, I can say it's not a lot of work, particularly if you'd be
getting the package compiling for your own purposes anyway.

If you (where, by "you", I mean anyone reading this!) want to try taking
over the maintainership, there's a bunch of information about what's
required at https://cygwin.com/packaging-contributors-guide.html, and
the packagers' mailing list is active and helpful.  Plus -- while we
seem to have mostly dropped the habit of awarding gold stars to folk
making contributions -- I think adopting an orphaned package is still
worthy of automatic listing at https://cygwin.com/goldstars/

Adam

  reply	other threads:[~2022-02-15 12:39 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 [this message]
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
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=20220215123941.yxesbunapq3gaxgq@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).