IN THE FILELISTS ARE SOME LETTERS USED. HERE AN EXPLANAITON:
[[T:][U,(
The optional characters at the beginning are flags. Here are their meanings:
T: This file should be considered a template file (i.e. copied into the domain, and not hardlinked)
U,(<user>|admin): this file should be owned by the top level user <user>, or by the site admin (if admin is given). This will generally be used with T:, although it could be hard-linked. If hard-linked, the user parameter must be a top-level user, and not the special keyword admin. While expected to be rarely used, one example would be if you wanted to hardlink in an apache-owned file into each domain.
G,(<group>|admin): similar to U:, except that this controls the group ownership
L: Indicates that this file is a symlink that should be created. <filename2> must be specified, and will be what the created symlink will point to. Symlinks imply the T: flag, since hardlinked symlinks aren't supported over NFS.
M,<mode>: this file should be created with the permissions as given in <mode>. <mode> may be specified as octal (with a leading 0), hexidecimal (leading 0x), or integer. The common case would be to specify it as octal.
C: this file should be taken from the root filesystem but placed in a different location under the domain filesystem. <filename2> must be specified. For example, you might have the line "/usr/lib/opcenter/sendmail/install/sendmail.mc.site // /etc/mail/sendmail.mc"
R: this path is a directory, and all files under it should be handled recursively.
P: this path is a permanent template file, and should not be removed or updated under the templates directory.
A: this file should always be updated.
S,<pkg type>: The end of the line contains a package name and pattern. The contents of the package should be listed, and the pattern applied to the list. The resulting list of files will be added to the manifest as if they were listed separately with the rest of the flags given on the original line. If the pattern begins with an !, then the pattern is used to remove files from the package's manifest.
N: should only be specified along with the S flag. Specifies that this package should not be considered a strict dependency of the containing fst package.
I: Include files that aren't listed in the package file list, but are generated / owned by that package. Example of such file are the files generated in %post scriptlet of rpm.
<filename> and <filename2> must be absolute paths.