Top priorities:
* Use info_TEXINFOS
-* Figure out how to handle MANS
-
+* Figure out how to handle MANS:
+ * use man_MANS? Or man1_MANS, man2_MANS, etc?
+ * François wants man pages not to be installed by default.
+ in this case an additional "install-man" target would exist
+* Must rewrite am_install_var. Should break into multiple functions.
+ This will allow the callers to be a little smarter.
+* Use "$o" instead of "$(kr)o". This might be better if MS-DOS is ever
+ supported.
* am_error should use printf-style arguments (for eventual gettext scheme)
uninstall and pkg-dirs should rm -rf the dir.
-Merge dist*.am files into automake itself; replication is bad.
+Merge dist*.am files into automake itself; replication is bad. In
+general most .am files should be merged into automake. For instance
+all the "clean" targets could be merged by keeping lists of things to
+be removed. This would be a lot nicer looking. Note that the install
+targets probably should not be merged; it is sometimes useful to only
+install a small part.
Clean up the output:
* Order rules sensibly
* Eliminate extraneous rules when possible (eg 'install-am' stuff)
* Make sure vertical spacing is correct
* pretty-print targets
+* regularize how backslash-newline is done. Just one space between text
+ and backslash should be the rule. Update makefile-mode to allow this.
+ (set column to 0, probably)
Need OTHER_SOURCES to hold sources whose objects end up in eg LIBOBJS.
Dependency tracking should work here. Maybe if it doesn't exist it
install-info doesn't have to look in build directory for info files;
just don't support this mode.
+ [ actually I think this mode is required if the user is a maintainer
+ who is doing a non-srcdir build ]
Write autoconf macro to do all work necessary for automake. Eg define
PACKAGE, VERSION, etc.
Internationalize. [ gettext doesn't have the necessary machinery yet ]
+write test suite
+
================================================================
For CONFIG_HEADER,
It would be really interesting to be able to easily (as the end-user)
make many different versions of the library: shared, static, profiling,
debug, optimized...
+ How does Perl handle this?
X Must ranlib libraries after installing
Some examples to keep in mind while doing this:
================================================================
Have a program that generates a Makefile on stdout, passes it through
-a "config.status" style filter, and thence into make. Why bother,
+a "config.status"-style filter, and thence into make. Why bother,
other than the gee-whiz factor?
Would it be useful to integrate in some way with the Debian package