Eric Blake wrote:
> On FAT32 (which has no ACL support), one failure and one spurious output:
>
> file_has_acl("tmpfile0") returned no, expected yes
> FAIL: test-file-has-acl.sh
>
> setfacl: illegal acl entries
> PASS: test-copy-acl.sh
Thanks for testing. Can you show the complete output of
Hi Jim,
> FYI, building failed on Solaris 10,
>
> file-has-acl.c: In function 'acl_ace_nontrivial':
> file-has-acl.c:166: error: 'ALLOW' undeclared (first use in this function)
> file-has-acl.c:166: error: (Each undeclared identifier is reported only once
> file-has-acl.c:166: error: for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/8/2008 3:52 PM:
|
| * Cygwin. I tested only on a two-year old Cygwin.
|
| Testing can mean one of two things:
|
| 1) Create a test directory:
|./gnulib-tool --create-testdir --with-tests --dir=/tmp/testdir ac
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> So far, I'm done with the 'acl' module changes. Jim, for coreutils an
> appropriate NEWS entry is:
>
> Improved support for access control lists (ACLs): On MacOS X, Solaris 7..10,
> HP-UX 11, Tru64, AIX, IRIX 6.5, and Cygwin, "ls -l" now di
Hi all,
So far, I'm done with the 'acl' module changes. Jim, for coreutils an
appropriate NEWS entry is:
Improved support for access control lists (ACLs): On MacOS X, Solaris 7..10,
HP-UX 11, Tru64, AIX, IRIX 6.5, and Cygwin, "ls -l" now displays the presence
of an ACL on a file through a '
