|What to do in case of errors|
|First, please read the documentation to rule out the possibility that it's just a badly written sentence that caused misunderstanding. |
|The internal design|
|Entry data storage.|
|The basic data structure for entries; an entry can be a file, directory, or special node (symlink or device). |
|Debugging and error checking.|
|Depending on configure options (|
|A list of variables that can be set by commandline parameters or environment variables; these are used in nearly every action. |
|apr_hash_t *||ign___groups = NULL|
|All groups, addressed by name. |
I highly appreciate any help, tips and tricks, and even if it's just a bug report I want to know that.
I'm also looking forward to documentation updates, and notifying me about mistakes will be politely answered, too.
|apr_hash_t* ign___groups = NULL|
All groups, addressed by name.
Groups have to be considered as follows:
added manually, they should apply as usual
The easiest way seems to be to write the properties in the filesystem when the entries are allocated for being stored in the entry list, ie. at
commit time. The simplest way to do that would be in waa__output_tree() - we see that an entry is newly allocated, and push all (not already set) properties there. But that wouldn't work with the
prop-del command, as an automatically assigned property wouldn't get removed.
So there's the function ops__apply_group(), which is called in the appropriate places.
Referenced by ign___new_group().