Am Dienstag, 6. September 2011, 19:14:57 schrieb Phil Holmes: > > -----Original Message----- > > From: Graham Percival [mailto:gra...@percival-music.ca] > > The only kind of person who's interested in those other > > repositories will have their own favorite directory layout > > anyway (like me; all my source repositories go under > > $HOME/src/) so they'd ignore any recommendation anyway. > > Wouldn't it be better to standardise them so that the doc and website > builds can copy them using standard scripts?
No, the doc and website build MUST NOT depend on anything that is not part of the lilypond git repo. Anything else does not simplify things, but rather complicates the build by one more dependency (which we then also have to check for in the ./configure script, properly document in the instructions, and most importantly also have to regularly update/fetch to keep the main build working)... The idea here is not to split up the current codebase to multiple repositories. Rather, we have some branches in our git repository, which do not have anything to do with the lilypond codebase. The proposal is to move that code out of the lilypond git repository and into their own. Lilypond will not depend on those other repositories at all. cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
