Bruno Haible <[EMAIL PROTECTED]> wrote: > Hi Jim, > > I'm currently writing 3 unit tests for the 'acl' module functionality: > test-set-mode-acl > test-copy-acl > test-file-has-acl > > and accordingly I think the file 'acl.c' should be renamed to > 'set-mode-acl.c'. > 'acl.c' is one particular functionality: it sets ACLs of a particular kind > on files (only ACLs which correspond to file modes). It is not the most > low-level > part of the module (file-has-acl.c is more low-level), and not the > highest-level > part either (copy-acl.c is higher level). > > If we someday want a wrapper API which allows access to internals of the ACLs, > independently whether they are POSIX-draft style, or Solaris style, or HP-UX > style, or AIX style, or older AIX style, _that_ should be called acl.c. (With > such a wrapper API the coreutils chmod program could be used to manipulate > ACLs > in a platform independent way...) > > OK to rename the file?
That makes sense. Thanks!
