Comment #11 on issue 1964 by pkx1...@gmail.com: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964
Well I have some comments that may be valid.
1. $LILYPOND_GIT/.git/config doesn't contain 'staging' after you use
lily-git.tcl to pull down the code.
So following the various threads on dev I manually added a second line to
my config file manually to include staging
--snip--
[remote "origin"]
url = git://git.sv.gnu.org/lilypond.git
fetch = +refs/heads/master:refs/remotes/origin/master
fetch = +refs/heads/staging:refs/remotes/origin/staging <--Added
by me
--snip-
I looked at Lily-git.tcl and could see where we pull down the tree
--snip--
git init
git config core.bare false
git remote add -t $originHead \
origin git://git.sv.gnu.org/lilypond.git
git fetch
git reset --hard origin/$originHead
git config branch.$originHead.remote origin
git config branch.$originHead.merge refs/heads/$originHead
--snip-
but couldn't see how $originHead was defined in lily-git.tcl.
I wonder, as lily-dev is for people like myself (or for those like Alberto
that want to submit a patch but are not on Linux and so need an
easy-to-setup build environment) whether $originHead should be 'staging'
not 'master' instead?
I realise that this is not necessarily to do with LilyDev but wasn't sure
how easy it was to incorporate a change like this into Lily-git.tcl that we
put in ../skel/.. on lilydev in the first place.
2. echo $PATH doesn't include '$LILYPOND_GIT/build/out/bin/' by default.
Personally I find this would be useful, again to those that just want
to 'get on with stuff' as we are advocating using an out-of-tree build
process to configure and make, after which the above path contains the
lilypond and lilypond-book commands (that I often use when making document
edits for testing) using the 'current' build and this means that devs would
not need to think they have to make-install just to test something quickly.
So adding this path to the bash.rc (or wherever - .profile?) would be nice
I think.
So far other than those, it;s been ok. There are another slew of updates
from canonical that I will apply and continue to test so that if we do cut
a new Lilydev we can include those.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
