Please note that the original report should have read,
"However, note that any directory returned HAS been confirmed to exist,
and need NOT be checked further"
Adam K
Bugs in Module-Install-CustomInstallationPath via RT wrote:
Show quoted text> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "NOTICE: Critical changes to File::HomeDir API",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned an ID of [rt.cpan.org #19335]. Your ticket is accessible
> on the web at:
>
>
http://rt.cpan.org/Ticket/Display.html?id=19335
>
> Please include the string:
>
> [rt.cpan.org #19335]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
> Thank you,
> bug-Module-Install-CustomInstallationPath@rt.cpan.org
>
> -------------------------------------------------------------------------
> You are receiving this bug report because you are a use of File::HomeDir.
>
> Please note that in a few months, a significant change will be made to
> File::HomeDir.
>
> Currently, all methods in the newer API are documented as always
> returning a directory.
>
> Some downstream code may be relying on this.
>
> Note that shortly, File::HomeDir will be changed so that for
> environments in which there is NO logical home directory, File::HomeDir
> will return C<undef> (even in list-context cases). This is intended to
> create warnings or error, rather than potentially cause a silent change
> in behaviour (if it returned '' or the null list).
>
> However, note that any directory returned will still have been confirmed
> to exist, and need to be checked further.
>
> This bug has been filed pro-actively, you should resolve it once you
> have confirmed that your module can handle false values being returned
> for the home directory.
