Behaviours common to any win32 os for config::find
# don't use Config::Find::WinAny; use Config::Find;
Implements features common to all the Win32 \s-1OS\s0's
This module implements Config::Find for Win32 \s-1OS\s0's.
\s-1WARNING\s0!!! Configuration file placement has changed on version 0.15 to be more Windows friendly (see note below).
Order for config files searching is... (see note at the end for entries marked as 1b and 2b)
1 ${LOCAL_APPDATA}/$name.cfg [user] (1b /$path_to_script/Users/$user/$name.cfg [user]) 2 /$path_to_script/$name.cfg [global]
unless when $ENV{${name}_HOME} is defined. That changes the search paths to...
(1b $ENV{${name}_HOME}/Users/$user/$name.cfg [user]) 2 $ENV{${name}_HOME}/$name.cfg [global]
When the \*(L"several configuration files in one directory\*(R" aproach is used, the order is something different...
1 ${LOCAL_APPDATA}/$dir/$name.cfg [user] (1b /$path_to_script/Users/$user/$dir/$name.cfg [user]) 2 /$path_to_script/$name.cfg [global] (2b /$path_to_script/$dir/$name.dfg [global])
(it is also affected by $ENV{${name}_HOME} variable)
Note: entries marked as 1b were the default behaviour for versions of Config::Find until 0.14. New behaviour is to put user application configuration data under ${\s-1LOCAL_APPDATA\s0} as returned by \*(C`Win32::GetFolderPath(CSIDL_LOCAL_APPDATA)\*(C' (if this call fails, the old approach is used). Also, global configuration files were stored under a new directory placed in the same dir as the script but this is unnecesary because windows apps already go in their own directory.
It seems that, sometimes, ${\s-1LOCAL_APPDATA\s0} points to the user desktop and placing configuration files there would be obviusly wrong. As a work around, the module will ignore ${\s-1LOCAL_APPDATA\s0} or ${\s-1APPDATA\s0} if they point to any place below the desktop path.
None by default.
Config::Find, Config::Find::Any
Salvador Fandin\*~o, <[email protected]>
Copyright 2003 by Salvador Fandin\*~o
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.