Hey José. If you are willing to learn, you should first try compiling lilypond from the source on the git repository. Google ³compiling lilypond² for the documentation. This takes about a day (if you¹re lucky I was lucky, and I still had to update/download many-a-program and do a manual override on my config file to get it to find certain fonts). Once you have a lilypond git repository established, let me know. If this sounds un-fun, I would very much recommend waiting until this becomes part of lilypond: compiling lilypond requires comfort with the shell Terminal that is rather far adrift from the Mac OS X prefab version of lilypond. Word on the street is that this process will be easier in future versions of lilypond, although that is not a part of lilypond development that I know well, and I am not competent enough to tell you how far away that is from being a reality.
I would also not suggest copy-and-pasting my new scheme and postscript files into your working directory it is generally bad practice. If you do this and there winds up being a bug that I didn¹t catch, you will have another problem on your hands that is much more precipitous than the potential problems associated with compiling. Again, compiling is a serious time and learning commitment that you should ONLY bring upon yourself if you want to develop. Otherwise, I will do my best to integrate your recommendations into the work I¹ve already done, and as Carl said, this will be part of lilypond in the not too distant future :-) Cheers, ~Mike On 6/10/10 3:49 AM, "josé henrique padovani" <[email protected]> wrote: > Em 09/06/10 22:04, Graham Percival escreveu: >> >> On Wed, Jun 09, 2010 at 09:41:34PM -0300, josé henrique padovani wrote: >> >> >>> >>> Em 09/06/10 21:23, Carl Sorensen escreveu: >>> >>> >>>> >>>> Unfortunately, it doesn't include the complete files, so it would be fairly >>>> difficult for a user who is not familiar with git or patch to make it work. >>>> >>>> >>>> >>> >>> Could you please give some advices about which git / patch flags should >>> I use to apply the patch to my current directories? >>> >>> >> >> >> If you seriously want to learn, then do a google search for >> "patch" to learn how to use it. If not, wait a few weeks until >> it's part of lilypond. This topic is too long to teach in a few >> emails. >> >> Cheers, >> - Graham >> >> > Hi Graham, > > I did already used patch and diff in some codes... > but I have no experience about how to use it with git (I have seen that the > patch was created with a flag "--git" for diff, which I didn't found in diff > man) and don't know which commands should I use to download from the > lilypond's git repository... (just some tips would help me) > > > I mean: I am not sure about which git flags/address/etc should I use to > download the code.. (I suppose I should use git to download them and not > simply download the diffs with from > http://codereview.appspot.com/download/issue1425041_1.diff) > > Regarding patch, I would like to know if I should simply call it like this: > cd /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ (I'm > on a Mac) > patch < path-of-diffile/difffile.diff > > or if I should use some flags and/or call it from another place... > > Althought I am new to this process I think I can do it and would really > appreciate some help. > > Thank you, > josé > > > > > > >
_______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
