Re: Dealing with tarballs that tarbomb

2007-04-06 Thread Blair Zajac
On Apr 5, 2007, at 8:20 PM, Juan Manuel Palacios wrote: On Apr 5, 2007, at 7:05 PM, Blair Zajac wrote: Elias Pipping wrote: On Apr 6, 2007, at 12:21 AM, Blair Zajac wrote: Thanks, that's what I ended up going with, however, using file mkdir ${worksrcpath} instead of the system. how

Dealing with tarballs that tarbomb

2007-04-05 Thread Blair Zajac
The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean way to deal with this in MacPorts? I looked at specifying some extract

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Daniel J. Luke
On Apr 5, 2007, at 3:54 PM, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean way to deal with this in

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Eric Hall
On Thu, Apr 05, 2007 at 12:54:33PM -0700, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean way to deal

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Blair Zajac
Daniel J. Luke wrote: On Apr 5, 2007, at 3:54 PM, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean way to

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Blair Zajac
Eric Hall wrote: On Thu, Apr 05, 2007 at 12:54:33PM -0700, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Blair Zajac
Elias Pipping wrote: On Apr 6, 2007, at 12:21 AM, Blair Zajac wrote: Thanks, that's what I ended up going with, however, using file mkdir ${worksrcpath} instead of the system. how about 'xinstall -d'? Don't the 'file subcommands' commands not shell out? Which is a good thing to

Re: Dealing with tarballs that tarbomb

2007-04-05 Thread Juan Manuel Palacios
On Apr 5, 2007, at 7:05 PM, Blair Zajac wrote: Elias Pipping wrote: On Apr 6, 2007, at 12:21 AM, Blair Zajac wrote: Thanks, that's what I ended up going with, however, using file mkdir ${worksrcpath} instead of the system. how about 'xinstall -d'? Don't the 'file subcommands' commands