Actually, subversion can be used for this task. Just store the permissions as properties. This also allows you to store ACLs, have version control (and check-in notes) on the permission changes, etc, etc...

A useful resource would probably be the various API bindings. From this you can use the check-in/check-out hooks to do something like:

    use SVN::Client;

    my $svn = new SVN::Client();
    $svn->propset("acl:joe", "rw", $target, 0, 0);

    # Where $target is the local (checked out) copy

[download]

NB. The SVN perl bindings are NOT in CPAN. You need to get them along with subversion. (Discussion)

If anyone needs me I'll be in the Angry Dome.

In reply to Re: Permissions Utility Script for sysadmins - seeking comments by idsfa
in thread Permissions Utility Script for sysadmins - seeking comments by BuddhaNature

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.