[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installing COPYING whatever the previous `value'

From: Alexandre Duret-Lutz
Subject: Re: Installing COPYING whatever the previous `value'
Date: Mon, 14 Oct 2002 18:47:56 +0200
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu)

>>> "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
missing          -- requirable by AM_INIT_AUTOMAKE
mkinstalldirs    -- requirable by AM_INIT_AUTOMAKE
py-compile       -- requirable by AM_PATH_PYTHON (*)

That leaves two files.

(*) 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.
Alexandre Duret-Lutz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]