Add support for @LongLink

[piranna]

GNU tar use @LongLink to set when the next entry will have a long name. This is used in the GCC and Linux kernel .tar.gz files, so when using tar-stream to de-compress them some files are not extracted and other times there are EACCESS errors.

[piranna]

/home/piranna/Proyectos/NodeOS/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/scripts/preinstall.js:35
  if(error) throw error;
                  ^
Error: EACCES, open '/home/piranna/Proyectos/NodeOS/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/deps/gcc/@LongLink'
    at Error (native)

[piranna]

I've found the same problem is happening when extracting Node.js source code:

#!/usr/bin/env node

var Download = require('download');


// Source versions

const NODEJS_VERSION = "v0.11.14"


// Source URLs

const NODEJS_URL="http://nodejs.org/dist/"+NODEJS_VERSION+"/node-"+NODEJS_VERSION+".tar.gz"


Download({ extract: true, strip: 1 })
.get(NODEJS_URL, 'deps/node')
.run(function(error)
{
  if(error) throw error;

  console.log('Download finished!');
})

download uses internally tar-stream.

[mafintosh]

Fixed in 1.1.4 \o/

[piranna]

👍