csjewell ([personal profile] csjewell) wrote,
@ 2010-03-16 03:35 pm UTC
Entry tags:strawberry perl
die(), or die() not ... there is no try().
  —Yoda, on exceptions in Perl.

Well, as the Perl Foundation blog says, I'm working on getting relocation working, and it'll be a race to see what gets done first: getting relocation working, or Perl 5.12.0 RC0.

Once both are done, I'll release the first betas for the April cycle.

Right now, I've hooked in a "choose the location" dialog into the installer for 5.11.5+ versions, and I've just finished blocking the ability to install into a directory with spaces.

(Unfortunately, until I can safely run dmake (which I know does not work) and all the other modules in the toolchain that Perl relies on in a directory with spaces, I'm blocking the ability to install into a directory with spaces. There is a code to get around it, if you REALLY want to know... but you have to ask me for it, and I can't support it if you do.)

The other "unfortunately" that's a problem is perl RT#73562, which is going to prevent 5.10.1 from being relocated if I don't get a patch I can use for it.

(Read 2 comments) - (Post a new comment)
(Flat) (Top-level comments only)

It's wrong


[identity profile] zloy-russkiy.livejournal.com
2010-03-17 08:17 am UTC (link)
I checked. dmake.exe works good with quoting, i.e. "c:\somepath\path with spaces" works.

(Reply to this)  (Thread) 


Re: It's wrong


[personal profile] csjewell
2010-03-17 04:16 pm UTC (link)
That may be true, but that's not the only thing we need to check for space-compatibility.

1) Does dmake work when you generate makefiles that refer to files with spaces, and is quoting required or not in that situation? Remember that Win32::GetShortPathName() may not always work - it will NOT work if shortname generation is turned off on the drive in question - which is sometimes done for speed reasons on servers.
2) Does ExtUtils::MakeMaker generate Makefiles that work when @INC has directories with spaces in it?
3) Does ExtUtils::ParseXS parse .xs files and output C files in directories with spaces?
4) Does ExtUtils::CBuilder work and do the compilation work for Module::Build with a space-containing @INC?
5) Does Module::Build work with @INC having directories with spaces in it?
6) Heck, does perl not bail out or split things wrong when you hand it a directory with spaces in @INC?

That's what I meant by "all the other modules in the toolchain" earlier.

Those will all need checked (they may work, I just don't know) - and there's probably other things I haven't mentioned - before I'm willing to support installing into directories with spaces.

Probably a good thing to check after the April releases.

(Reply to this)  (Thread from start)  (Parent) 


(Read 2 comments) - (Post a new comment)
(Flat) (Top-level comments only)