Re: Perl, Windows, & env.pm

It's Windows (lack of) case sensitivity that's causing the problems as derby points out. Best thing to do might be to make your env module something like OurCompanyName::Env, or OurProductName::Env (i.e. have a custom directory for your company/product specific modules).

Comment on Re: Perl, Windows, & env.pm

Replies are listed 'Best First'.
(OT) Re^2: Perl, Windows, & env.pm by Argel (Prior) on Aug 14, 2007 at 23:42 UTC
It's Windows (lack of) case sensitivity.... What's really sad is that the file system (NTFS) is actually case sensitive (it has to be for POSIX compliance but I'm not sure if that's why that was designed in).	[reply]
Re^3: Perl, Windows, & env.pm by holli (Abbot) on Aug 14, 2007 at 23:51 UTC
the file system (NTFS) is actually case sensitive It's not. It's only case preserving. holli, /regexed monk/	[reply] [d/l]
(OT) Re^4: Perl, Windows, & env.pm by Argel (Prior) on Aug 15, 2007 at 19:59 UTC
Actually, NTFS is case sensitive thanks to POSIX compliance. You can read more about it in Filenames are Case Sensitive on NTFS Volumes from Microsoft's Knowledge Base. The Windows system calls and APIs do by default behave in a case preserving manner. But you are confusing what Windows allows you to normally do with the actual filesystem. I say "by default" because with some registry tweaking Windows can become case sensitive as well, though I imagine this would break a lot of things (I also hear it is harder to enable this under Windows 2003). Update: Sime minor rewording.	[reply]