public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gerrit P. Haase" <freeweb@nyckelpiga.de>
To: cygwin@sources.redhat.com
Subject: Re: new site for my ports is up
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <6922205099.20011115174508@familiehaase.de> (raw)
In-Reply-To: <3BF3C479.B1E97461@wapme-systems.de>

Hallo Stipe,

2001-11-15 17:43:21, du schriebst:

>> BTW, is it possible to introduce a new path like '/opt' e.g. for Apache, or
>> should it better go in /usr/apache, /usr/mysql ...?

> I have to veto here!

Ok.

> Apache goes by default to /usr/local/apache and should reside there
> for a cygwin based binary package that I'm currently preparing :))

> That way we take two with one: 1) cygwin's policy for /usr/local is
> consistently helf, 2) apache's default layout path is taken.

Default is default, but it doesn't matter if you install it in /opt/apache,
/www/apache, /usr/apache, /usr/local/apache, the layout is always the same,
just the prefix is different.

Gerrit
-- 
convey Information Systems GmbH                   http://www.convey.de/
                                                  Vitalisstraße 326-328
Gerrit P. Haase                                   D-50933 Köln
gerrit.haase@convey.de                            Fon: ++49 221 6903922


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-11-15 16:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  8:26 Gerrit P. Haase
2001-11-11  8:26 ` Charles Wilson
2001-11-11  8:26   ` Christopher Faylor
2001-11-11  8:26     ` Gerrit P. Haase
2001-11-11  8:26       ` Robert Collins
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26         ` Gerrit P. Haase [this message]
2001-11-11  8:26           ` Stipe Tolj
2001-11-11  8:26         ` Robert Collins
2001-11-11  8:26           ` Stipe Tolj
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26       ` Charles Wilson
2001-11-11  8:26         ` John Marshall
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26             ` Christopher Faylor
2001-11-11  8:26               ` Charles Wilson
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26                 ` Christopher Faylor
2001-11-11  8:26                   ` Robert Collins
2001-11-11  8:26                     ` Christopher Faylor
2001-11-11  8:26           ` Robert Collins
2001-11-11  8:26             ` Jochen Küpper
2001-11-11  8:26               ` Stipe Tolj
2001-11-11  8:26                 ` Jochen Küpper
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26           ` Robert Collins
2001-11-11  8:26             ` Stipe Tolj
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26 Robert Collins
2001-11-11  8:26 ` Christopher Faylor
2001-11-11  8:26   ` Robert Collins
2001-11-11  8:26     ` Christopher Faylor
2001-11-11  8:26   ` Christopher Faylor
2001-11-11  8:26     ` Charles Wilson
2001-11-11  8:26       ` Christopher Faylor
2001-11-11  8:26 David A. Cobb

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=6922205099.20011115174508@familiehaase.de \
    --to=freeweb@nyckelpiga.de \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@sources.redhat.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).