public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stipe Tolj <tolj@wapme-systems.de>
To: Robert Collins <robert.collins@itdomain.com.au>
Cc: "Gerrit P. Haase" <cygwin@cygwin.com>
Subject: Re: new site for my ports is up
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <3BF44E43.131ED7C9@wapme-systems.de> (raw)
In-Reply-To: <05c601c16e23$68c9f060$0200a8c0@lifelesswks>

> Why should apache go to /usr/local/apache? Name one redhat/suse/debian
> style amanaged linux distribution that puts apache there! The configure
> script for _any_ package will need parameters given to it when building
> a package to be included in cygwin.
> 
> Until now, no-one as raised the issue of changing _our_ standard, which
> is that setup.exe installed software installs into / and /usr, not into
> /usr/local. And I do not think we should change that. I don't believe
> that the users will be served by us installing into /usr/local.

If you consider point 3) from down I agree. There are some packages
that do install into  /usr/local, or am I wrong here?!

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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 23:22 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         ` Robert Collins
2001-11-11  8:26           ` Stipe Tolj [this message]
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26         ` Gerrit P. Haase
2001-11-11  8:26           ` Stipe Tolj
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 David A. Cobb
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   ` Robert Collins
2001-11-11  8:26     ` Christopher Faylor

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=3BF44E43.131ED7C9@wapme-systems.de \
    --to=tolj@wapme-systems.de \
    --cc=cygwin@cygwin.com \
    --cc=robert.collins@itdomain.com.au \
    /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).