On Thu, Jul 14, 2005 at 07:11:41AM -0400, Joshua Kronengold wrote:
> On Thu, 14 Jul 2005 6:37 am, Michael G Schwern wrote:
> >One of the things Cwd tries is `pwd`. It doesn't work because it
> >doesn't
> >have any more information to go on than Perl does.
>
> Wow.
> Um -- what are the perms on t
On Thu, 14 Jul 2005 6:37 am, Michael G Schwern wrote:
One of the things Cwd tries is `pwd`. It doesn't work because it
doesn't
have any more information to go on than Perl does.
Wow.
Um -- what are the perms on the directory in question? I'd expect this
behavior for perms set to, say, 000 -
On Wed, Jul 13, 2005 at 07:43:13PM -0400, Joshua Kronengold wrote:
> On Wed, 13 Jul 2005 7:17 pm, Michael G Schwern via RT wrote:
> >The bleadperl version tries both getcwd() and cwd(). Both fail.
> >In fact, nothing works:
>
> I think shelling out usually works (on unixlike systems) as a last
>
On Wed, 13 Jul 2005 7:17 pm, Michael G Schwern via RT wrote:
The bleadperl version tries both getcwd() and cwd(). Both fail.
In fact, nothing works:
I think shelling out usually works (on unixlike systems) as a last
resort.
On Wed, Jul 13, 2005 at 09:58:44AM -0500, Joshua Kronengold wrote:
> OTOH, I -was- able to replicate it on Solaris (SunOS 5.8) with perl
> 5.6.2 (work is very conservative in terms of perl versions) (stock
> FindBin).
>
> The test program was:
>
>
> #!/usr
Rafael Garcia-Suarez via RT writes:
>On 7/13/05, Michael G Schwern via RT <[EMAIL PROTECTED]> wrote:
>> > [EMAIL PROTECTED] - Wed Dec 01 06:23:20 1999]:
>> > Possible solutions:
>> > Fix Cwd::abs_path(), so it doesn't do that. Possibly, rather
>IIUC that was probably fixed by change #24375 o
On 7/13/05, Michael G Schwern via RT <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] - Wed Dec 01 06:23:20 1999]:
> >
> > Possible solutions:
> > Fix Cwd::abs_path(), so it doesn't do that. Possibly, rather
> > than warning and returning, it should use fast_abs_path() instead,
> > which sho
> [EMAIL PROTECTED] - Wed Dec 01 06:23:20 1999]:
>
> Possible solutions:
> Fix Cwd::abs_path(), so it doesn't do that. Possibly, rather
> than warning and returning, it should use fast_abs_path() instead,
> which should handle warnings if they need to be given.
> Alternatively, have
