# from Eric Wilhelm
# on Monday 12 January 2009 15:38:

>>As long as this release, unlike 0.31, doesn't result in 100% FAIL on
>>Windows then I'm happy.
>
>As far as I know, this should fail everywhere that 0.31 did.  Where
> did we break since 0.30 and what is being done about it?
>
>A big feature of the 0.31 release was supposed to be that it *fixes* a
>bug specific to win32.  Please tell me we've got our numbers mixed.

Oh my.  Indeed.

And nobody noticed it or mentioned it for 3 months (let alone the set of 
two alphas starting over a month ago.)

Can we perhaps find anyone who cares enough to automatically monitor 
trunk for breakage?



$ svn diff -r 11884:HEAD t/tilde.t
Index: t/tilde.t
===================================================================
--- t/tilde.t   (revision 11884)
+++ t/tilde.t   (revision 12418)
@@ -4,7 +4,7 @@

 use strict;
 use lib $ENV{PERL_CORE} ? '../lib/Module/Build/t/lib' : 't/lib';
-use MBTest tests => 17;
+use MBTest tests => 18;

 use_ok 'Module::Build';
 ensure_blib('Module::Build');
@@ -68,6 +68,13 @@
     is( run_sample( prefix => '~' )->prefix,
        $home );

+    # Test when HOME is different from getpwuid(), as in sudo.
+    {
+        local $ENV{HOME} = '/wibble/whomp';
+
+        is( run_sample( $p => '~' )->$p(),    "/wibble/whomp" );
+    }
+
     my $mb = run_sample( install_path => { html => '~/html',
                                           lib  => '~/lib'   }
                       );

------------------------------------------------------------------------
r11900 | schwern | 2008-09-28 15:03:26 -0700 (Sun, 28 Sep 2008) | 4 
lines

 r67...@windhund:  schwern | 2008-09-28 18:02:37 -0400
   - Fix ~ expansion when $HOME is different from /etc/passwd as
     when running sudo.  [rt.cpan.org 39662]


--Eric
-- 
The only thing that could save UNIX at this late date would be a new $30
shareware version that runs on an unexpanded Commodore 64.
--Don Lancaster (1991)
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to