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
Message-ID:	<089601c15693$73a44050$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Roth, Kevin P." <KPRoth AT MarathonOil DOT com>,
	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>,
	"Corinna Vinschen" <cygwin-apps AT cygwin DOT com>
References:	<6EB31774D39507408D04392F40A10B2BACC613 AT FDYEXC202 DOT mgroupnet DOT com>
Subject:	Re: cURL packaging progress
Date:	Wed, 17 Oct 2001 08:39:27 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	16 Oct 2001 22:45:18.0681 (UTC) FILETIME=[3AEC7C90:01C15694]

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).

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 :].

Rob

----- Original Message -----
From: "Roth, Kevin P." <KPRoth AT MarathonOil DOT com>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>; "Corinna Vinschen"
<cygwin-apps AT cygwin DOT com>
Sent: Wednesday, October 17, 2001 6:27 AM
Subject: RE: cURL packaging progress


Considering it appears I was BCc'd (and the list wasn't copied), I'm
responding just to you two.

I believe curl will be completely cygwin compliant (with all necessary
readme's, etc) as it is distributed from curl.haxx.se. For this reason,
I could do one of two things for submitting source tarballs to cygwin
(once curl is accepted as an official package):

1: submit in original form (meaning it will unpack as curl-7.9.1),
although
   we could easily change the name of the tar file to match.

2: download, untar, 'mv curl-7.9.1 curl-7.9.1-1', retar. This sounds
like
   more work, considering I would "typically" never expect to make any
   cygwin releases that didn't correspond to new curl releases. In other
   words, in most cases there will never be a curl-7.9.1-2.

I'm guessing #2 is your preference, however I'm just wondering if you're
open to accepting #1 in this case (obviously if there WERE a need to
release an interim cygwin version, it would then have to be named
appropriately and repackaged...)

--Kevin


> -----Original Message-----
> From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
> Sent: Tuesday, October 16, 2001 4:18 PM
> To: Corinna Vinschen
> Subject: Re: cURL packaging progress
>
>
>
>
> Corinna Vinschen wrote:
>
> > Oops, Chris missed the release number in the example:
> >
> >   curl-1.2.3-1.tar.bz2
> >
> > The source analogous
> >
> >   curl-1.2.3-1-src.tar.bz2
> >
> > The source should unpack into a directory exactly named as the
> > archive
> >
> >   curl-1.2.3-1/
>
>
> Oops. I didn't know this. I've been doing <srctop> = curl-1.2.3, not
> curl-1.2.3-1.
>
> --Chuck
>
>
>

- Raw text -