Re: [PATCH] docs: how to work around checks on invalid primary/directory couples

[Ralf Wildenhues]

> > +pkglib_PROGRAMS = foo
> > +doc_LIBRARIES = libquux.a

Another nit: can we find less obviously bogus combinations that users
might actually want to use?  It is sometimes necessary to put _DATA in
libdir (if only because there is no automake primary for the file
type).  I'm not sure I know of a good example of an exec file that would
belong outside of the exec dirs; after all, the other directories are
supposed to be either shareable between different operating systems, or
possibly non-executable or so.

Thanks,
Ralf