Bug #61042 for App-perlbrew: Broken on solaris

Fri Sep 03 16:46:25 2010 NNUNLEY [...] cpan.org - Ticket created

Subject:

Broken on solaris

The assumption that the system tar is gnu tar is unfortunate. Under solaris, if gnu tar is installed at all, it is named 'gtar'. Your best strategy is to use the same detection methods that work with cpanminus -- check to see if your using gnu tar -- it so, use the simple method. If not, use the old fashioned way or try to find gtar: b?zcat perl...tar | tar xf -

Sat Jan 08 00:07:32 2011 DOHERTY [...] cpan.org - Correspondence added

On Fri Sep 03 16:46:25 2010, NNUNLEY wrote: Show quoted text

> The assumption that the system tar is gnu tar is unfortunate. Under > solaris, if gnu tar is installed at all, it is named 'gtar'. > > Your best strategy is to use the same detection methods that work with > cpanminus -- check to see if your using gnu tar -- it so, use the

simple Show quoted text

> method. If not, use the old fashioned way or try to find gtar: b?zcat > perl...tar | tar xf -

Doesn't ptar exist for this reason?

Sat Jan 08 00:07:33 2011 The RT System itself - Status changed from 'new' to 'open'

Sat Feb 12 17:41:43 2011 DOHERTY [...] cpan.org - Cc DOHERTY added

Sat Feb 12 18:00:06 2011 DOHERTY [...] cpan.org - Correspondence added

Subject:

[PATCH] Untarring broken on Solaris

On Fri Sep 03 16:46:25 2010, NNUNLEY wrote: Show quoted text

> The assumption that the system tar is gnu tar is unfortunate. Under > solaris, if gnu tar is installed at all, it is named 'gtar'. > > Your best strategy is to use the same detection methods that work with > cpanminus -- check to see if your using gnu tar -- it so, use the simple > method. If not, use the old fashioned way or try to find gtar: b?zcat > perl...tar | tar xf -

This patch simply attempts to use gtar if running on Solaris: https://github.com/doherty/App- perlbrew/commit/a9bf148a7e17ea05d31a7a96310525602c8a6d42

Mon Feb 14 04:42:24 2011 GUGOD [...] cpan.org - Correspondence added

在 2010-九月-03 16:46:25 星期五時，NNUNLEY 寫到： Show quoted text

> The assumption that the system tar is gnu tar is unfortunate. Under > solaris, if gnu tar is installed at all, it is named 'gtar'. > > Your best strategy is to use the same detection methods that work with > cpanminus -- check to see if your using gnu tar -- it so, use the simple > method. If not, use the old fashioned way or try to find gtar: b?zcat > perl...tar | tar xf -

NNUNLEY: Can you grab this executable and test it on your Solaris? https://github.com/gugod/App-perlbrew/raw/develop/perlbrew Let me know if that works for you. Thanks.

Mon Feb 14 22:34:51 2011 DOHERTY [...] cpan.org - Correspondence added

On Mon Feb 14 04:42:24 2011, GUGOD wrote: Show quoted text

> Can you grab this executable and test it on your Solaris?

I did test this, and it works if gtar can be found in $PATH. However, the better solution is to use Archive::Tar instead of hoping the executable is present.

Tue Feb 15 19:00:50 2011 DOHERTY [...] cpan.org - Correspondence added

On Mon Feb 14 22:34:51 2011, DOHERTY wrote: Show quoted text

> On Mon Feb 14 04:42:24 2011, GUGOD wrote:

> > Can you grab this executable and test it on your Solaris?

> > I did test this, and it works if gtar can be found in $PATH. However,

the Show quoted text

> better solution is to use Archive::Tar instead of hoping the executable > is present.

That'd be the Archive::Tar that is a Perl module that uses the Perl that... we haven't extracted or built yet. D'oh!

Thu Feb 24 20:06:33 2011 mutant.nz [...] gmail.com - Correspondence added

From:

mutant.nz [...] gmail.com

It's not true that gnu tar installed on Solaris will always be named 'gtar'. For instance, if you've installed the tar package from sunfreeware.com, it will be named 'tar' (it's just that it'll be installed under /usr/local/bin, and solaris tar will still be there under /usr/bin). Ideally both names should be checked for, and possibly even some heuristics added to see if a particular tar 'looks like' gnu tar. I might rustle up a patch if I get a chance.

Thu Feb 24 20:26:05 2011 nnunley [...] gmail.com - Correspondence added

CC:	NNUNLEY [...] cpan.org, DOHERTY [...] cpan.org
Subject:	Re: [rt.cpan.org #61042] Broken on solaris
Date:	Thu, 24 Feb 2011 20:25:15 -0500
To:	bug-App-perlbrew [...] rt.cpan.org
From:	Norman Nunley <nnunley [...] gmail.com>

On Thu, Feb 24, 2011 at 8:06 PM, Sam Crawley via RT < bug-App-perlbrew@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=61042 > > > It's not true that gnu tar installed on Solaris will always be named > 'gtar'. For instance, if you've installed the tar package from > sunfreeware.com, it will be named 'tar' (it's just that it'll be > installed under /usr/local/bin, and solaris tar will still be there > under /usr/bin). >

Blastwave (blastwave.org) installs gnu tar as gtar under /opt/csw/bin. In general, it seems that they have a preference for prefixing gnu equivalents to commands already in the Solaris core system distribution with a 'g'. Show quoted text

> > Ideally both names should be checked for, and possibly even some > heuristics added to see if a particular tar 'looks like' gnu tar. I > might rustle up a patch if I get a chance. >

I submitted a similar patch to Miyagawa for cpanm. App::cpanm does have iterate through several locations of tar, and verifies that tar --version includes text from the GNU tar header.

Mon Sep 15 13:27:41 2014 NHORNE [...] cpan.org - Correspondence added

On Thu Feb 24 20:06:33 2011, Mutant wrote: Show quoted text

> It's not true that gnu tar installed on Solaris will always be named > 'gtar'. For instance, if you've installed the tar package from > sunfreeware.com, it will be named 'tar' (it's just that it'll be > installed under /usr/local/bin, and solaris tar will still be there > under /usr/bin). > > Ideally both names should be checked for, and possibly even some > heuristics added to see if a particular tar 'looks like' gnu tar. I > might rustle up a patch if I get a chance.

Correct. Perlbrew is broken on some Solaris derivatives such as Dyson because of this. Why not use the value of tar in CPAN::Config?