automake-ng
[Top][All Lists]
Advanced

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

[Automake-ng] [PATCH 4/4] [ng] deptrack: remove obsolescent comments


From: Stefano Lattarini
Subject: [Automake-ng] [PATCH 4/4] [ng] deptrack: remove obsolescent comments
Date: Thu, 26 Jan 2012 14:44:23 +0100

* lib/am/depcomp2.am: Remove some comments describing the why and
the how of the verbosity and organization of the recipes.  Since we
are heavily refactoring and re-organizing the code, such comments
are doomed to get out-of-sync with the new layout and/or behaviour
of the code.  If the need arises, we will re-introduce an updated
version of the comments in a future changeset.
And since we are at it, improve another unrelated comment.
---
 lib/am/depend2.am |   32 ++++----------------------------
 1 files changed, 4 insertions(+), 28 deletions(-)

diff --git a/lib/am/depend2.am b/lib/am/depend2.am
index 7592aba..cc2f85c 100644
--- a/lib/am/depend2.am
+++ b/lib/am/depend2.am
@@ -29,34 +29,10 @@
 ##   the `if AMDEP' chunk is prefix with @AMDEP_TRUE@ just like for any
 ##   other configure-time conditional.
 ##
-## We do likewise for %FASTDEP%; this expands to an ordinary
-## configure-time conditional.  %FASTDEP% is used to speed up the
-## common case of building a package with gcc 3.x.  In this case we
-## can skip the use of depcomp and easily inline the dependency
-## tracking.
-
-## Verbosity of FASTDEP rules
-## --------------------------
-## (1) Some people want to see what happens during make.  They think
-##     @-commands are evil because hiding things hinders debugging.
-## (2) Other people want to see only the important commands--those that
-##     may produce diagnostics, such as compiler invocations.  They
-##     do not care about build details such as dependency generation
-##     (the if/then/else machinery in FASTDEP rules).  Their point is
-##     that it is hard to spot diagnostics in a verbose output.
-## (3) Other people want `make -s' to work as expected: silently.
-##     This way they can spot any diagnostic really easily.
-##
-## The second point suggests we hide rules with @ and that we `echo'
-## only the relevant parts.  However this goes against the two others.
-## There are regular complaints about this on the mailing list, but
-## it's hard to please everybody.  On April 2003, William Fulton (from
-## clan (3)) and Karl Berry (from clan (2)) agreed that folding the
-## compile rules so that they are output on a single line (instead of 5)
-## would be a good compromise.  Actually we use two lines rather than one,
-## because this way %SOURCE% is always located at the end of the first
-## line and is therefore easier to spot.  (We need an extra line when
-## depbase is used.)
+## We do likewise for %FASTDEP%; this expands to an ordinary configure-time
+## conditional.  %FASTDEP% is used to speed up the common case of building
+## a package with gcc >= 3.x.  In this case we can skip the use of depcomp
+## and easily inline the dependency tracking.
 
 if %?FIRST%
 ?SUBDIROBJ?am__depdir = $(dir $@)/$(DEPDIR)
-- 
1.7.7.3




reply via email to

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