From: James Lowe <pkx166h@gmail.com>
Date: Sun, 1 Apr 2012 18:09:09 +0000 (+0100)
Subject: Doc: CG Update compile.itexi for doc build
X-Git-Tag: release/2.15.37-1~23
X-Git-Url: https://git.donarmstrong.com/lilypond.git?a=commitdiff_plain;h=539eb86b35a1269be607c4554b0fae6aa8d897ec;p=lilypond.git

Doc: CG Update compile.itexi for doc build

Issue 2416

There should no longer be a need to 'touch' soe files when
wanting to rebuild doc after making changes.

Removed @knownissue describing this.

Edited next para so it made syntactical sense running on from the
now previous para.
---

diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi
index c3aa45de1c..933f5c9829 100644
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -672,53 +672,10 @@ done separately by issuing:
 make info
 @end example
 
-@knownissues
-
-If source files have changed since the last documentation build,
-output files that need to be rebuilt are normally rebuilt, even if
-you do not run @code{make@tie{}doc-clean} first.  However, build
-dependencies in the documentation are so complex that some
-newly-edited files may not be rebuilt as they should be; a
-workaround is to @command{touch} the top source file for any
-manual you've edited.  For example, if you make changes to a file
-in @file{notation/}, do:
-
-@example
-touch Documentation/notation.tely
-@end example
-
-@noindent
-The top sources possibly affected by this are:
-
-@example
-Documentation/extend.texi
-Documentation/changes.tely
-Documentation/contributor.texi
-Documentation/essay.tely
-Documentation/extending.tely
-Documentation/learning.tely
-Documentation/notation.tely
-Documentation/snippets.tely
-Documentation/usage.tely
-Documentation/web.texi
-@end example
-
-@noindent
-You can @command{touch} all of them at once with:
-
-@example
-touch Documentation/*te??
-@end example
-
-@noindent
-However, this will rebuild all of the manuals
-indiscriminately---it is more efficient to @command{touch} only
-the affected files.
-
 @noindent
-Another typical issue when switching branches between master and
-lilypond/translation is the appearance/disappearance of translated
-versions of some manuals.  If you see such a warning from make:
+An issue when switching branches between master and lilypond/translation
+is the appearance/disappearance of translated versions of some manuals.
+If you see such a warning from make:
 
 @example
 No rule to make target `X', needed by `Y'