This error currently causes installation failure for modules MooseX-App-Cmd-0.30, Dancer-1.3134, and probably others.

That is never a convincing argument (it breaks some other modules test)

OTOH, this particular bug is so old and stupid, the docs got updated (tmpdir of File::Spec::Win32) to warn about it and disagree with the spec (tmpdir of File::Spec)

So the bugs as I see them in File::Spec are

• The last ditch directory is supposed to be the current directory ( File::Spec->curdir ) not / or /tmp
• / is a stupid directory to include / hardcode in the list
• either taint everything, including the hard coded values ,
• or untaint all the paths -- hybrid approach is stupid and inconvenient -- either you're helping/convenient/untainting, or you're letting the user deal with it

The bugs in File::Temp are

• it lets File::Spec get away with being stupid when it knows how stupid it is :) if it doesn't deal with the tainting its useless
• either do the job of tmpdir only better,
• or croak warning the user to untaint %ENV manually supply an untainted tmpdir manually (api change)

Current situation is inconveniencing everyone who tries to use either or both of these modules

FWIW, these are all variation of the same bug (not doing what the "spec" says, and the spec being stupid old/vague/akward/not useful )
Bug #76663 for PathTools: ->tmpdir on MSWin32 often returns the root-dir
Bug #70492 for PathTools: Re: Bug #60406 for PathTools: tmpdir with -T on Windows
Bug #60406 for PathTools: tmpdir with -T on Windows
Bug #29015 for PathTools: tmpdir() on Cygwin needs filetest pragma
Bug #74349 for PathTools: TMPDIR is being cached for the life of the module

update: Oh look some discussion on this Bug #120593 for perl5: File::Spec::Unix->tmpdir: Always return an absolute path

the arguments seem very weak and unconvincing

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.