tcpip49 / r-u-dead-yet

Automatically exported from code.google.com/p/r-u-dead-yet
0 stars 0 forks source link

tarball does not contain the directory for extracted files #2

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. gunzip R-U-Dead-Yet-v2.0.tar.gz
2. tar xvf R-U-Dead-Yet-v2.0.tar
3. Files are extracted directly the current working directory. It is normally 
expected that the extracted files should go under a created directory  (with 
name "R-U-Dead-Yet-v2.0") by the tarball.

What is the expected output? What do you see instead?

# tar xvf R-U-Dead-Yet-v2.0.tar 
Dead-Yet-v2.0/
BeautifulSoup.py
README.txt
rudeadyet.conf
r-u-dead-yet.py
socks.py
#

What version of the product are you using? On what operating system?
v2.0

Please provide any additional information below.

output of gunzip and tar:

# gunzip R-U-Dead-Yet-v2.0.tar.gz 
# tar xvf R-U-Dead-Yet-v2.0.tar 
BeautifulSoup.py
README.txt
rudeadyet.conf
r-u-dead-yet.py
socks.py
# ls
BeautifulSoup.py   ethtool-6.tar.gz  rudeadyet.conf   R-U-Dead-Yet-v2.0.tar
README.txt       r-u-dead-yet.py  socks.py
# 

it would be nice if the files get extracted within a directory called 
'R-U-Dead-Yet-v2.0'

Original issue reported on code.google.com by keshavap...@gmail.com on 22 Nov 2010 at 1:42

GoogleCodeExporter commented 8 years ago
Will improve on my compression routine next time

Original comment by ravivr@gmail.com on 8 Jan 2011 at 1:34