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
Subject: Re: /setup.html please read
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: cygwin-apps AT cygwin DOT com
In-Reply-To: <20011102134725.G26975@redhat.com>
References: 
	<6EB31774D39507408D04392F40A10B2BC1FDBD AT FDYEXC202 DOT mgroupnet DOT com> 
	<20011102134725 DOT G26975 AT redhat DOT com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1004745291.9086.74.camel@lifelesswks>
Mime-Version: 1.0
X-Mailer: Evolution/0.15 (Preview Release)
Date: 03 Nov 2001 10:58:56 +1100
X-OriginalArrivalTime: 03 Nov 2001 00:03:11.0832 (UTC) FILETIME=[ED5C7D80:01C163FA]

On Sat, 2001-11-03 at 05:47, Christopher Faylor wrote:
> On Fri, Nov 02, 2001 at 12:23:12PM -0500, Roth, Kevin P. wrote:

> >2) Under "Making Packages", I think the "standard" for binary packages
> >is to leave off the initial "/" on filenames inside the tarball.  E.g.:
> >    usr/doc/cURL-7.9/README
> >instead of
> >    /usr/doc/cURL-7.9/README
> >I think the point is to allow someone to expand the binary package into
> >some other location (besides "/") if desired for whatever reason.
> 
> I think this is implied by:
> 
> 	* Binary packages are extracted in /, include all file paths from the
> 	root in your archive.
> 
> Actually, this should be:
> 
> /usr/doc/cygwin/cURL-7.9-1.README
> or
> /usr/doc/cygwin/cURL-7.9.README

In the tarball it needs to be usr/doc/cygwin/cURL-7.9-1.README doesn't
it? (for correct manual extraction).

Hmm, I'll have to dig beep into tar.cc to answer this - Chris what is
the impact of skipping a leading / ?
 
> >3) I realize this one is kind of nit-picky, but the 4th bullet under
> >"Making Packages" mentions a "file" named /usr/doc/foo-vendor, when in
> >fact this should call it a "directory".
> 
> Actually, this is correct.   This should be a file.

Nope, directory. Sorry Chris :}.