[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilycontrib.tcl, was Re: the "r" in "git pull -r"

From: Jonathan Kulp
Subject: Re: lilycontrib.tcl, was Re: the "r" in "git pull -r"
Date: Tue, 11 Aug 2009 07:28:33 -0500

On Tue, Aug 11, 2009 at 7:00 AM, Jonathan Kulp <address@hidden> wrote:
On Tue, Aug 11, 2009 at 6:45 AM, Johannes Schindelin <address@hidden> wrote:
> So it doesn't give an error, just a warning. But AFAIR I have seen this
> warning on my non-GUI-based checkouts, too, even though everything
> worked fine. BTW, my git version is (the latest one that Ubuntu
> 9.04 has to offer).

Ouch, I think I know what happened.  Git used your _current_ working
directory as work tree.  So you have some stray LilyPond files lying
around somewhere.

Aha! That's why I found a bunch of lily files in my $HOME/bin/ directory! I found a lily/ directory inadvertently last night, and now that I look, there's the Documentation, ly, make, stepmake, etc. So the files did get downloaded, just not where expected. Easily fixed...


I chose an amateurish brute-force method but it worked. Here's my revised update_lilypond function:

proc update_lilypond {} {
       global lily_dir
       if {![file exists $lily_dir]} {
               file mkdir $lily_dir
               cd $lily_dir ; git init
               git config core.bare false
               cd $lily_dir ; git remote add -t master \
                       origin git://
               cd $lily_dir ; git fetch --depth 1
               cd $lily_dir ; git checkout -b master origin/master
       } else {
               cd $lily_dir ; git pull

It's possible that the first "cd $lily_dir" would suffice but I wanted to be sure without having to experiment.  I know that in some circumstances the next lines of scripts or makefiles the succeeding lines are run in the working dir rather than the target dir.

Thanks for the cool script, Johannes. :)

Jonathan Kulp

reply via email to

[Prev in Thread] Current Thread [Next in Thread]