public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Looking for new apache maintainer
Date: Thu, 27 May 2004 17:18:00 -0000	[thread overview]
Message-ID: <20040527162255.GB4740@coe.bosbc.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0405271205440.25579@slinky.cs.nyu.edu>

On Thu, May 27, 2004 at 12:09:29PM -0400, Igor Pechtchanski wrote:
>On Thu, 27 May 2004, Christopher Faylor wrote:
>>On Thu, May 27, 2004 at 08:55:02AM -0700, Brian Dessent wrote:
>>>Okay, I'll take that as an enthusiastic request for an apache2 package.
>>
>>FWIW: Me too! I think an apache2 package would be a very useful
>>addition.
>
>Ditto.
>
>Perhaps this should be moved to cygwin-apps (which Brian, as all other
>maintainers, will have to subscribe to anyway), but one more point
>while we're on the subject of Apache: maybe it's time to revisit the
>apache postinstall procedure (both the rebase issue and the /var/www
>one).  FWIW, one idea on the latter is splitting out the documents into
>a separate package (apache-docs?), installing over the manual, and
>using postinstall to set up the index.html.* files if they aren't
>present.  This way, "cygcheck -c" won't be confused by the apache
>packages anymore.  I can elaborate if there's interest.

One again, my assumptions catch up with me.  I was assuming that a new
package maintainer would be rethinking the packaging scheme.  Certainly
the current scheme could use some improvement.

But, yes, if we are going to be discusing this, then we should move to
cygwin-apps.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2004-05-27 16:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 11:38 Christopher Faylor
2004-05-27  8:19 ` Brian Dessent
2004-05-27  9:20   ` Christopher Faylor
2004-05-27  9:52   ` Max Bowsher
2004-05-27 10:05     ` Brian Dessent
2004-05-27 12:19       ` Max Bowsher
2004-05-27 12:40         ` Brian Dessent
2004-05-27 14:31       ` Andrew DeFaria
2004-05-27 14:43         ` Christopher Faylor
2004-05-27 15:13         ` Brian Dessent
2004-05-27 15:39           ` Andrew DeFaria
2004-05-27 16:09             ` Brian Dessent
2004-05-27 16:26               ` Christopher Faylor
2004-05-27 16:47                 ` Igor Pechtchanski
2004-05-27 17:18                   ` Christopher Faylor [this message]
2004-05-27 18:15                   ` Brian Dessent
2004-05-28 11:26                   ` Reini Urban
2004-05-27 21:25               ` Max Bowsher

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=20040527162255.GB4740@coe.bosbc.com \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --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).