> Well I certainly don't mind putting more things in the FAQ. We could
> start with a patch as you suggested above. Care to suggest one?
>
> Thanks,
> Ralf
I have attached a patch expanding the section about data files. Of
course feel free to correct any obvious mistakes since believe it or
not, I am not a native English speaker :-)
Matej
diff --git a/doc/automake.texi b/doc/automake.texi
index 265a3f8..a8c2068 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -6837,6 +6837,32 @@ Here is how Automake declares its auxiliary data files:
dist_pkgdata_DATA = clean-kr.am clean.am @dots{}
@end example
+If you have a project with lots of data files that sometimes change
+their names (for example computer games under developement) and you are
+thinking about telling Automake to install whole directory with its
+contents like
+
[EMAIL PROTECTED]
+dist_pkgdata_DATA = my_datadir
[EMAIL PROTECTED] example
+
+then be warned that it's not possible to do this. You have to specify all filenames
+of files you want to install or distribute. @xref{wildcards, ,Why doesn't Automake support wildcards?}
+for reasoning.
+
+Just remember you can use @code{nobase_} prefix (see @ref{Alternative, , An Alternative
+Approach to Subdirectories}), which is useful if your data
+files are organized in subdirectories. If you use it, you can just provide full
+filenames and subdirectories will be created during installation.
+
+They won't be removed in the uninstall process even if they are empty, though.
+The files will be removed after uninstall (this is due to GNU coding standards).
+
+You may have temptation to help yourself with writing shell scripts as @code{install-data-local}
+(see @ref{Extending, , Extending Automake Rules} if you need to inspire yourself)
+to bypass the neccessity of providing all the filenames. Anyway, if you decide to use
+your custom procedures, remember to at least run @code{make distcheck}, that may warn
+you if you forget something.
@node Sources
@section Built sources
