Comment #42 on issue 1635 by philehol...@googlemail.com: clean up misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I was working down the road of adding the known missing directories to the list of known missing files, and then not printing the warning if we know about the directory. However, we pass the location of the known-missing-file list on the command line, so for this to work, we would need to impose an order on the parameters in the calling line, which I'm uncomfortable with. The only alternative to that would appear to be to note an error has occurred, and then print the details after we've parsed the command line and got the list of known-missing-files. I'm OK with doing that, if it seems worth the effort. Otherwise the options would be to leave the error message (it's not very big) but make it more informative; or to just delete it. Thoughts?
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
