New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module Loading on Case-Insensitive File Systems #6480
Comments
From david@kineticode.comThis is a bug report for perl from david@kineticode.com, An issue has just come up with Stas Bekman's release of Apache::Test. It turns use constant HAS_APACHE_TEST => eval {require Apache::Test}; The problem, however, is that those of us who have already installed mod_perl This appears to be because although HFS+ is a case-insensitive file system, it mercury# find . -name "Test.pm" Note that when I told `find` to search for "test.pm" it didn't find any Stas and I are discussing other strategies for overcoming this problem. But if Thanks! David Flags: Site configuration information for perl v5.8.0: Configured by david at Sat Dec 21 18:17:50 PST 2002. Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration: Locally applied patches: @INC for perl v5.8.0: Environment for perl v5.8.0: |
From @eserteDavid Wheeler (via RT) <perlbug-followup@perl.org> writes:
I don't know how things are actually implemented, but my guess is that For a workaround one could do something like this (in pseudo code): open modulefile Also, I am not sure how to determine whether a file system is Regards,
-- |
From david@kineticode.comOn Thursday, May 1, 2003, at 11:45 AM, slaven@rezic.de (via RT) wrote:
Yes, that makes sense. We're using Perl's readdir in Apache::Test to
Correct, though in practice few use it. Does Config.pm know? I know Regards, David |
From @doughera88On Mon, 5 May 2003, David Wheeler wrote:
Alas, we can't assume that the filesystem where perl was built is also the -- |
From david@kineticode.comOn Tuesday, May 6, 2003, at 07:39 AM, Andy Dougherty (via RT) wrote:
Yes, I knew that. It just seemed the safest assumption. The only other Regards, David |
From @jkeenanOn Tue May 06 10:11:19 2003, david@kineticode.com wrote:
There has been no further discussion in this ticket in over 10 years. So I'm taking this ticket for the purpose of closing it in 7 days unless Thank you very much. |
From @HugmeirOn Fri, Aug 30, 2013 at 10:37 PM, James E Keenan via RT <
I believe this should stay open. The bug is still present and leads to It strikes me that this and non-ascii modules are in the same bag; Perl has Perhaps, if we could settle on some way to unambiguously represent module |
From @xdgOn Fri, Aug 30, 2013 at 10:39 PM, Brian Fraser <fraserbn@gmail.com> wrote:
Acme::require::case "solves" this by asking the parent directory for a I'm fine with the ticket staying open. Just because we don't have a David -- |
From victor@vsespb.ru2013/8/31 David Golden <xdg@xdg.me>
Non-ascii modules can suffer also from Unicode normalization (NFC/NFD) on
Possible optimization would be to determine case-sensitiveness of Then use Acme::require::case algorithm for directories on case-insensitive
|
From david@kineticode.comOn Aug 30, 2013, at 7:40 PM, Brian Fraser via RT <perlbug-followup@perl.org> wrote:
Man, I’m *old*.
I agree it is still present, but it could perhaps be closed by documenting how all this stuff is supposed to work. Best, David |
Almost seventeen years! Damn. I'm impressed the community elects to keep something like this open all that time, despite not much complaint, always with the thought to properly resolve it at some point. Thanks Perl for such a resilient process. |
Migrated from rt.perl.org#22077 (status was 'open')
Searchable as RT22077$
The text was updated successfully, but these errors were encountered: