Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
From:	"Gerrit P. Haase" <gp AT familiehaase DOT de>
Organization:	Esse keine toten Tiere
To:	"Roth, Kevin P." <KPRoth AT MarathonOil DOT com>, <cygwin-apps AT cygwin DOT com>
Date:	Wed, 17 Oct 2001 09:43:14 +0200
MIME-Version:	1.0
Subject:	Re: cURL packaging progress
Reply-to:	cygwin-apps AT cygwin DOT com
Message-ID:	<3BCD52B2.15688.55D83410@localhost>
In-reply-to:	<089601c15693$73a44050$0200a8c0@lifelesswks>
X-mailer:	Pegasus Mail for Win32 (v3.12cDE)
X-Hops:	1
X-Sender:	320081107336-0001 AT t-dialin DOT net

Robert Collins schrieb am 2001-10-17, 8:39:

>Kevin, I presume you will be creating a /usr/doc/curl-7.9.1/README file
>that at a minimum lists the configure options you used to allow a user
>to rebuild the package.. (I'm not sure that this convention is
>documented outside this lists archives).

Isn't the 'Cygwin'-README always located/named at 
/usr/doc/Cygwin/curl-7.9.1.README?

>If so then that README should also be included in your src tarball, so
>that a user who uninstalls the binary when they grab the source doesn't
>lose the info.
>
>That means you will be repacking the tarball anyway, so renaming isn't
>that hard :].


-- 
=^..^=

- Raw text -