[4suite-dev] ACL set vs add

[Mike Brown]

In the followup to an old/closed bug report, Mike Olson wrote:

  One note, the ACL that is displayed is the "inherited ACL"
  so if you look at the ACL for an object, at it shows that
  there are three people allowed to read it, then you add
  another, you will lose the original three.

This is completely unintuitive. Currently there seems to be
no difference between using set and add. The Quick Start doc
appendix B says

  set - to completely replace existing specific ACL permission with 
        a new set you specify

  For example, if you wanted to set permission of Write ACL to "uo", 
  then type "s".

  Enter the type of access as write and the username to set as "uo".

  The others super-users and owners (that you can see above) will be
  replaced by "uo".

  Then only "uo" will have permission to write to that container, 
  in this case /home/uo.


  add - to add additional users to a specific ACL permissions list

  For example, if you wanted to add user "uo" to the Write ACL, 
  then type "a" and enter the type of access as write and the
  username to set as "uo". "uo" will be added to the existing list
  of users.


If you follow the directions, you get the exact same results for
both set and add:

  Write ACL
    uo --> allowed

My impression is that the results for 'add' should be different, but
your note above makes it sound like the display doesn't reflect the
real ACL, or maybe it does and this is the expected behavior.. or something.

Help.