Comment #12 on issue 1635 by [email protected]: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
OK - here's a proposal to get rid of just 3 warnings. I realise this isn't
the bulk, but it's come up as part of understanding what's going on.
It looks like there's an assumption that the @includes for the document
philsguide.tely are generally in the directory Documentation/philsguide.
extract*.py therefore checks to see if the directory exists - if it does,
it appends it to the search path. If it doesn't, it prints an error
message:
if os.path.isdir (a):
include_path.append (a)
else:
print 'NOT A DIR from: ', os.getcwd (), a
Can't see any point in printing that error message, unless we change the
Documentation directory structure such that there is *always* a
subdirectory for each major document. An example of where there isn't is
changes.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
