🚀 go-pugleaf

In article <m3og84e8ra.fsf@thyme.td.micromuse.co.uk>, Tim Haynes wrote:
>philh@vision25.demon.co.uk (phil hunt) writes:
>
>> The way i do this is that first I create a directory parrot-0.2.5/ which
>> contains evereything I want to include from the parrot/ directory to go
>> into the tarball. This is potentially error-prone, especially as it is a
>> routine (& therefore boring) administrative task. Then I execute the tar
>> command above.
>
>It's a question of directory paths. If you want the contents of the tar
>archive to be 
>	blah-0.2
>	blah-0.2/Minutes.doc
>	blah-0.2/cd_b4.tar.gz
>	blah-0.2/somefile.txt
>
>then you must be in a directory containing blah-0.2/ underneath it; the
>alternatives are either full directory paths (EVIL! [1]) or no directories
>at all (  cd blah-0.2 ; tar cvzf ../blah-0.2.tar.gz * )  according to taste.
>
>> Is there an easier way?
>
>   -1) that IS easy!  ;8^]

:-)
Another possibility, create a directory that will be like the one you want
the unpacking to produce - put into it a symbolic or hard link to each of
the files you want to be found in it.

-- 
Richard Robinson
"The whole plan hinged upon the natural curiosity of potatoes" - S. Lem