# Re: Archive::Tar uncompress question

**URL:** <https://www.ruby-forum.com/t/re-archive-tar-uncompress-question/93702>\
**Category:** Ruby\
**Created:** [April 6, 2006, 9:28pm UTC](https://www.ruby-forum.com/t/re-archive-tar-uncompress-question/93702 "2006-04-06T21:28:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BergerS\_Daniel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/bc8723/32.png) [@BergerS\_Daniel](https://www.ruby-forum.com/u/BergerS_Daniel)\
**Post date:** [April 6, 2006, 9:28pm UTC](https://www.ruby-forum.com/t/re-archive-tar-uncompress-question/93702/1 "2006-04-06T21:28:32Z")

</div>

> -----Original Message-----  
> From: Austin Z. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]  
> Sent: Thursday, April 06, 2006 1:17 PM  
> To: ruby-talk ML  
> Subject: Re: Archive::Tar uncompress question

> I’m not sure. I’m just surprised that tarsimple uses  
> Archive::Tar as its name, instead of Archive::Tar::Wrapper or  
> something like that, since it’s just a wrapper, and not a tar  
> implementation in Ruby.
> 
> -austin

Are you (or anyone else) using Archive::Tar for minitar or something?

But yeah, I should probably change that to Archive::Tar::External, which  
would be in line with my Net::Ping::External (a convention I adopted  
from Perl, btw), although I highly doubt anyone would use both packages  
in the same program.

Dan

---

<div class="post-metadata">

**Author:** ![BergerS\_Daniel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/bc8723/32.png) [@BergerS\_Daniel](https://www.ruby-forum.com/u/BergerS_Daniel)\
**Post date:** [April 6, 2006, 9:34pm UTC](https://www.ruby-forum.com/t/re-archive-tar-uncompress-question/93702/2 "2006-04-06T21:34:43Z")

</div>

On 4/6/06, Berger, Daniel [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > I’m not sure. I’m just surprised that tarsimple uses Archive::Tar as  
> > its name, instead of Archive::Tar::Wrapper or something like that,  
> > since it’s just a wrapper, and not a tar implementation in Ruby.  
> > Are you (or anyone else) using Archive::Tar for minitar or something?
> 
> But yeah, I should probably change that to Archive::Tar::External,  
> which would be in line with my Net::Ping::External (a convention I  
> adopted from Perl, btw), although I highly doubt anyone would use both  
> packages in the same program.

I’m using it as a namespace in minitar (Archive::Tar::Minitar), which  
just declares it as a module. I can be a bit smarter about how I declare  
it, so it’s not a huge deal; I was just surprised that the package name  
and the namespace mismatched so wildly 😉

-austin