Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Mon, 14 Apr 2003 18:32:47 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: crypt...
Message-ID:	<20030414163247.GB32658@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<00b601c3028d$65a9d8a0$3f33fea9 AT HAPPYCOMPUTER>
Mime-Version:	1.0
In-Reply-To:	<00b601c3028d$65a9d8a0$3f33fea9@HAPPYCOMPUTER>
User-Agent:	Mutt/1.4.1i

On Mon, Apr 14, 2003 at 11:38:39PM +1000, Gareth Pearce wrote:
> I was wondering if (other than for someone to actually do it) there was some
> explicit reason for crypt to be seperate to cygwin?  Sort of makes
> satisfying SUSv2 unistd.h impossible...  I see its optional in SUSv3 ...
> Sure its simple to work arround, but it would be nice if it 'just worked'.

It was originally included to get passwords for 9x.  It doesn't fit into
Cygwin itself due to licensing constraints.  Therefore an extra library.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -