Re: Installing COPYING whatever the previous `value'

[Akim Demaille]

| >>> "Akim" == Akim Demaille <address@hidden> writes:
|  Akim> Ha, it's true I forgot that sometimes Automake is making the decision
|  Akim> (e.g., ylwrap).  My idea was that anything that has to be installed
|  Akim> can traced from configure.ac.  E.g., gettext could perfectly
|  Akim> AC_SOURCES([config.rpath]), and autolib could use this information.
| 
|  Akim> But, I agree, ylwrap is a counter example.  Are there many?
| 
| compile          -- requirable by AM_PROG_CC_C_O
| config.guess     -- requirable by AC_CANONICAL_* 
| config.sub       -- requirable by AC_CANONICAL_* 
| depcomp          -- requirable by AM_DEP_TRACK
| elisp-comp       -- requirable by AM_PATH_LISPDIR (*)
| install-sh       -- requirable by AM_INIT_AUTOMAKE
| mdate-sh
| missing          -- requirable by AM_INIT_AUTOMAKE
| mkinstalldirs    -- requirable by AM_INIT_AUTOMAKE
| py-compile       -- requirable by AM_PATH_PYTHON (*)
| ylwrap
| 
| That leaves two files.

Hm.  Do you think we should use AC_LIBSOURCE?  Or introduce a new
macro, which would ``type'' the files?  (I'm thinking for instance
that AC_LIBSOURCES should be in AC_CONFIG_LIBDIR).  Yeah, that would
be safer.  Maybe AC_REQUIRE_CONFIG_FILE, AC_REQUIRE_BUILD_FILE or
something.

| (*) Note that presently these helper scripts are required in
| packages where Python or Elisp files are built/installed.  This
| is somewhat finer that the simple use of an Autoconf macro.  For
| instance I could be running AM_PATH_PYTHON because I need Python
| X.Y during the build, and still don't need py-compile.

Arg.  Good point.

Still, at least to simplify our tools, I suggest that we handle the
others this way: introduce another macro, and have the proper AC and
AM macros require config.*, install-sh etc.

OK with you?

Would you make a suggestion about the name of the macro?