Archive::Tar uncompress question

ruby-talk
1

Yeah, I didn't want to take the package name 'archive-tar' because I
figured someone, some day, would write a version that would use a zlib
backend, i.e. a port of the Archive::Tar Perl module. So, I
intentionally named my package something else, but used Archive::Tar
internally because I figured no one would use an external wrapper *and*
a zlib wrapper - what would be the point?

To create even MORE confusion, it's listed as just 'tarsimple' on the
RAA because of a goofy 15 character limit on project names there.

Anyway, if minitar uses a zlib backend (I haven't looked in a long
while), then perhaps you ought to snag that project name for the RAA and
consider using that namespace instead. Obviously, that is strictly up
to you, but it might be more familiar to folks coming to Ruby from Perl
who are familiar with that package.

Regards,

Dan

···

-----Original Message-----
From: Austin Ziegler [mailto:halostatue@gmail.com]
Sent: Thursday, April 06, 2006 1:33 PM
To: ruby-talk ML
Subject: Re: Archive::Tar uncompress question

On 4/6/06, Berger, Daniel <Daniel.Berger@qwest.com> 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 :wink:

-austin

2

Minitar is so named because it's an incomplete implementation of the
tar format. It does have the ability to work against gzipped files.

There's more functionality hopefully coming.

-austin

···

On 4/6/06, Berger, Daniel <Daniel.Berger@qwest.com> wrote:

On 4/6/06, Berger, Daniel <Daniel.Berger@qwest.com> 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 :wink:

Yeah, I didn't want to take the package name 'archive-tar' because I
figured someone, some day, would write a version that would use a zlib
backend, i.e. a port of the Archive::Tar Perl module. So, I
intentionally named my package something else, but used Archive::Tar
internally because I figured no one would use an external wrapper
*and* a zlib wrapper - what would be the point?

--
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca