1) your solution will not work because the website is not built in the production area. A separate script copies the website, once it's
built, into
the web server directory. Your web/install.html will never be seen by
the web
server.
Because the script doesn't copy it. That would be easy to solve.
2) I would not accept this solution even if it worked, because it
involves weird
hard-coding for the old website.
Agreed. But solves an issue that is hanging around for.. one year? I am not selling this as the salvation for the world, but as a patch to remove that page from newbies looking from lilypond while no lilypond devel has 30 minutes to copy the PDF files :) Anyway, will try to find what files are being pointed by the new website. Cheers http://codereview.appspot.com/5500069/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
