delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/07/14/19:40:16

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 14 Jul 2004 19:40:07 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Robert R Schneck <schneck AT math DOT berkeley DOT edu>
cc: cygwin AT cygwin DOT com
Subject: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
In-Reply-To: <cd4fbt$uvn$1@sea.gmane.org>
Message-ID: <Pine.GSO.4.58.0407141937171.29800@slinky.cs.nyu.edu>
References: <401DE9E4 DOT 60E61FA2 AT dessent DOT net> <20040714013022 DOT 2CBDF85081 AT pessard DOT research DOT canon DOT com DOT au> <cd251o$t1e$1 AT sea DOT gmane DOT org> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040713222328 DOT 0335a278 AT pop DOT prospeed DOT net> <cd2dso$bnl$1 AT sea DOT gmane DOT org> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040714102705 DOT 03334178 AT pop DOT prospeed DOT net> <20040714150732 DOT GW1389 AT cygbert DOT vinschen DOT de> <cd4fbt$uvn$1 AT sea DOT gmane DOT org>
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.39

On Wed, 14 Jul 2004, Robert R Schneck wrote:

> Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> > I don't think cron should contain a dependency to ssmtp though.  It
> > would be the same as to have a dependency to exim.  And why should
> > cron.README contain hints about how to set up ssmtp?  That's the job
> > for the ssmtp README, isn't it?
>
> It might save people like this thread's original poster some detective
> work.  Though granted, it's not much work to figure out where sendmail
> points and then which README is relevant.  Perhaps the User's Guide
> should put a little more stress on the usefulness of
> /usr/share/doc/Cygwin.
>
> Robert

Yep, that would be a very good idea.  In particular, it should point out
that the information in the READMEs in /usr/share/doc/Cygwin takes
precedence over that in the package READMEs and manpages.

Maybe even an FAQ entry like "I've followed directions in the README / man
page / info file to the letter, and still can't get the package to work -
what gives?" (put in this form, it *is* rather frequently asked). :-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019