On Wed, 9 Oct 2013 07:42:43 -0400, "sisyphus1@optusnet.com.au via RT"
<bug-Text-CSV_XS@rt.cpan.org> wrote:
Show quoted text> > I expect that to be a problem in the available version of tar. The .tgz
> > files do have to be created with --format=ustar when using a modern GNU
> > tar.
>
> So this problem does apply *only* to .tgz files ?
No, to all files created with a GNU tar that has a different default
format than older tar versions.
FWIW GNU-tar-1.27' NEWS file does not mention any change in this regard
at all. I consider the change a tar bug.
Archive format selection:
-H, --format=FORMAT create archive of the given format
FORMAT is one of the following:
gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
v7 old V7 tar format
The manual pages of GNU tar do NOT mention anywhere what the default
is :(
Show quoted text> If so - no drama; I now know I just have to go to backpan if I want to get a
> usable source distro of a '.tgz' CPAN source tarball. (I think that the
> metacpan source might also be usable with the old GNU tar installations that
> I have ... I haven't properly tested that hypothesis ... don't even know
> what "metacpan" is :-)
>
> Just checked that a module I uploaded to CPAN a few days ago (a '.tar.gz'
> file) does not suffer from this abomination ... and, thankfully, it doesn't.
What tar did you use to create it? On what OS?
Show quoted text> Cheers,
> Rob
--
H.Merijn Brand
http://tux.nl Perl Monger
http://amsterdam.pm.org/
using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/