[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS branching etc
From: |
Erik Sandberg |
Subject: |
CVS branching etc |
Date: |
Wed, 21 Apr 2004 12:11:19 +0200 |
User-agent: |
KMail/1.5.4 |
hi,
I finally got CVS to work. So I'll soon upload the bug database to CVS. I
think I will create a separate branch lilypond_2_2 for bugs in that version.
Some questions have popped up:
1. What is the easiest way of invoking lilypond directly from the source tree?
I.e. how do I easily make ./scripts/out/lilypond
invoke ./lily/out/lilypond-bin instead of /usr/bin/lilypond-bin, and how do I
make it use ./scm/, etc. instead of /usr/share/lilypond/2.2.0/scm, etc?
(this is pretty crucial since I'll have to maintain bug databases for both 2.2
and 2.3; so I'll sometimes have to switch between versions just to compile a
single .ly file).
2. I'm about to create the new branch now. I don't want to screw anything up,
so can somebody please verify that the following command line is what I
should do?
~/lily-bugs$ cvs -z3 -d address@hidden:/cvsroot/lilypond import
lily-bugs 1.1.1 lilypond_2_2
(I beleive that this would create a new module lily-bugs
under /cvsroot/lilypond, containing all files in the current working
directory.. is this true?)
thanks,
Erik
- CVS branching etc,
Erik Sandberg <=