[p4] p4tar/p4untar in cygwin?
jgrills at drivensnow.org
Thu Oct 27 17:30:03 PDT 2005
Ah, bummer. I was testing with an actual changelist that I had in
development, and I didn't want to lose any changes, so I only had deletes in
my test p4tar. I already have plans for the evening so I don't think I'll
get to it tonight, but I will try soon.
It sounds like the next issue may be newline related. Those are typically
annoying but solvable.
From: Jay Glanville [mailto:Jay.Glanville at naturalconvergence.com]
Sent: Thursday, October 27, 2005 10:31 AM
To: Jeff Grills; Perforce Users Mailing List
Subject: RE: [p4] p4tar/p4untar in cygwin?
Thanks for your work Jeff.
Unfortunately, there is still a problem. Apparently, the elseif clause on
line 401 (elseif ($_ eq "")) is never true. Therefore, the p4untar command
will execute all the necessary p4 edit / add / delete / sync commands, but
it won't every copy the file contents over.
If I'm interpreting what this "while" block is doing is iterating over all
the fstat records, looking for an empty line to delineate between the
different file's records. I don't think that this empty line is being
Hope this helps.
> It was definitely that pipe. I've submitted a new version
> with a "-nopipe"
> command line option that works around the issue. I should probably
> eventually try to auto-detect cygwin perl and do this, but
> not tonight.
> I also found that if you use the cygwin version of p4
> it works just
> fine, but that doesn't have very good interoperability with
> p4v/p4win/standard p4 (for instance, it seems to have no
> registry support
> and also expects p4 tickets in different place).
> At least there is a solution for the night.
> -----Original Message-----
> From: Jay Glanville [mailto:Jay.Glanville at naturalconvergence.com]
> Sent: Wednesday, October 26, 2005 6:00 PM
> To: Jeff Grills; Perforce Users Mailing List
> Subject: RE: [p4] p4tar/p4untar in cygwin?
> I found that it would hang near line 123, in the
> subroutine/method PipeIn,
> either on the "open(PIPE..." or the "print PIPE ..." lines.
> I thus assumed
> that the cygwin perl interpreter had problems with pipes.
> Just my $0.02. My perl is so bad I wouldn't offer anything
> more then $0.02.
> > -----Original Message-----
> > From: Jeff Grills [mailto:jgrills at drivensnow.org]
> > Sent: Wednesday, October 26, 2005 6:43 PM
> > To: Jay Glanville; 'Perforce Users Mailing List'
> > Subject: RE: [p4] p4tar/p4untar in cygwin?
> > It's not just you. I haven't ever tried to figure out what the
> > issue is, though. Perhaps I'll have some time to look at it
> > tonight.
> > j
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com
> > [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Jay Glanville
> > Sent: Wednesday, October 26, 2005 8:29 AM
> > To: Perforce Users Mailing List
> > Subject: [p4] p4tar/p4untar in cygwin?
> > Hello P4'ers
> > Has anyone had any success with using Jeff's p4untar tool
> in a cygwin
> > environment? I think that there may be a problem with the perl
> > interpreter in cygwin and p4tar's usage of pipes.
> > The only way I could get results was if I uninstalled the perl
> > interpreter from cygwin and installed a Win32 perl interpreter from
> > ActiveState.
> > Has anyone else come across this problem? (i.e.: or is it just me?)
> > JDG
> > ---
> > Jay Dickon Glanville
> > _______________________________________________
> > perforce-user mailing list - perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user