GNU bug report logs - #13136
24.2; tar-ball packages created on windows do not work

Previous Next

Full log

Message #8 received at 13136 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: "Fidler\, Matt" <matt.fidler <at> alcon.com>
Cc: 13136 <at> debbugs.gnu.org
Subject: Re: bug#13136: 24.2; tar-ball packages created on windows do not work
Date: Mon, 10 Dec 2012 23:52:58 -0500

"Fidler, Matt" wrote:

> Any tar-ball package created with 7zip or with bsdtar includes the
>
> directory structure of a package as follows:
>
>
>
> org-readme-0.11
>
> org-readme-0.11\org-readme-pkg.el

Thanks for the report. Is this a valid tar file?
The zip format explicitly requires forward slashes [1], but I could not
find a clear answer one way or the other for tar.

http://www.gnu.org/software/tar/manual/html_node/Portable-Names.html#SEC137

says:

   Use portable file and member names. A name is portable if it contains
   only ASCII letters and digits, `/', `.', '_', and '-' [...]

http://www.gnu.org/software/tar/manual/html_node/Standard.html#SEC182

just says

   The name field is the file name of the file, with directory names (if
   any) preceding the file name, separated by slashes.

which is annoyingly vague.

Anyway, none of that really helps you...


[1] http://www.pkware.com/documents/casestudies/APPNOTE.TXT
  
  4.4.17.1 The name of the file, with optional relative path.
  
    The path stored MUST not contain a drive or device letter, or a
    leading slash. All slashes MUST be forward slashes '/' as opposed
    to backwards slashes '\' for compatibility with Amiga and UNIX
    file systems etc.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.