On Tue, Sep 06, 2011 at 06:25:34PM +0100, Phil Holmes wrote: > > -----Original Message----- > > From: Graham Percival [mailto:[email protected]] > > > > What about just using environment variables, $LILYPOND_GIT > > and $LILYPOND_MEDIA_GIT, then telling the user to set up > > these variables by themselves? (potentially after googling > > for help) That feels like a more "unix-y" solution to me. :) > > Surely it's better to put them in My Documents\lily\media, etc. :-) > > I'm reasonably easy, providing there's some standard way of accessing the > files. It just seems to me that if you're going to say "you must set up a > variable called LILYPOND_GIT pointing to your repository" you might as well > say "To use standard build methods, you must put the repositories in these > directories".
Honest answer? Because I want to use the standard build methods, but I'm not going to change my directory structure. Sure, there might be other people like me who would be spectactularly unimpressed with a project that insisted on hard-coding their directory paths and we don't want to turn away people like that, but really the biggest reason is my own convenience. On that note, I wonder if it would be worth standardizing everything on LILYPOND_GIT instead of $HOME/lilypond-git. There would be no change to lilydev people, since we'd set that up for them, so it's just a matter of changing all the scripts+docs appropriately. Then I wouldn't need the weird symlink on the webserver and more experienced developers can put their lilypond git repo wherever they want. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
