Mail Archives: cygwin-apps/2001/11/02/19:00:12
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 :}.
- Raw text -