Open djzhh opened 4 months ago
I had a look at https://github.com/tonycoz/perl5/commit/ddb756c358e14d22cc474e2a9925455716e45b36, a solution for https://github.com/Perl/perl5/issues/22067 , perhaps this might be a solution:
*** old/cpan/ExtUtils-Manifest/t/Manifest.t 2023-11-28 12:57:27.000000000 +0100
--- new/cpan/ExtUtils-Manifest/t/Manifest.t 2024-03-12 15:28:55.000000000 +0100
*************** is_deeply( $files, \%expect, 'maniadd()
*** 454,460 ****
#maniadd({ foo => 'bar' });
SKIP: {
! chmod( 0400, 'MANIFEST' );
skip "Can't make MANIFEST read-only", 2 if -w 'MANIFEST' or $Config{osname} eq 'cygwin';
eval {
--- 454,464 ----
#maniadd({ foo => 'bar' });
SKIP: {
! require Config;
! require File::Spec;
! my $Curdir = File::Spec->curdir;
! skip "AFS", 2
! if $Config{afs} eq "true" && ($Curdir eq '.' || $Curdir =~ /^\Q$Config{afsroot}/);chmod( 0400, 'MANIFEST' );
skip "Can't make MANIFEST read-only", 2 if -w 'MANIFEST' or $Config{osname} eq 'cygwin';
eval {
The require Config;
may be obsolete, though.
Test #93 fails on AFS filesystems, as on AFS
chmod
does not have any effect. Compilation with files located locally works though. Tested usingperl-5.36.3
andperl-5.38.2
.The test must fail as there is no such thing as file-based ACLs in AFS; see https://docs.openafs.org/UserGuide/HDRWQ46.html
Part of test code:
Setting the test file to read-only using
chmod 0400
will not provoke any error, which (so it seems to me) is expected in line 468. See the behaviour of AFS below:Perhaps a workaround analog to https://github.com/pmqs/IO-Compress/issues/56#issuecomment-1980388117 would be a solution.