bug#13136: 24.2; tar-ball packages created on windows do not work

[Fidler, Matt]

Glenn,

I'm sorry, I wasn't as clear as I could have been.  

The directory structure is actually

Org-readme-0.11
Org-readme-0.11/org-readme.pkg.el

The issue is that the directory entry does not include this forward slash when 
using bsdtar or 7zip under windows.  It doesn't matter if you include the 
forward slash in the tar command or 7zip command.

Matt.

-----Original Message-----
From: Glenn Morris [mailto:rgm@gnu.org] 
Sent: Monday, December 10, 2012 10:53 PM
To: Fidler, Matt
Cc: 13136@debbugs.gnu.org
Subject: Re: bug#13136: 24.2; tar-ball packages created on windows do not work

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