[Top][All Lists]

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

Re: Code review/discussion time again.

From: David Kastrup
Subject: Re: Code review/discussion time again.
Date: Sun, 22 Nov 2009 01:47:41 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)

Reinhold Kainhofer <address@hidden> writes:

> Am Sonntag, 22. November 2009 01:17:10 schrieb David Kastrup:
>> Neil Puttock <address@hidden> writes:
>> > 2009/11/21 David Kastrup <address@hidden>:
>> >> Modifying Lilypond, then recompiling and reinstalling.  That's not the
>> >> most hack-friendly way.  I am still finding my way around.
>> >
>> > You're only modifying .scm files, so there shouldn't be any
>> > recompiling/reinstalling involved.
>> They are lilypond .scm files, so I need to edit them either in the
>> source tree (where they won't get consulted without reinstalling) or in
>> the installed tree (where they will get overwritten on reinstalling) or
>> in private directories (where I get into search order mess when
>> different versions are flying around).
> The easiest way to develop lilypond is to execute the binary directly
> from the build tree (=source tree). In particular, I have a file
> ~/.bin/lilypond (~/.bin is in my $PATH) containing only:

> [...]

But the main point for me is that developing new functionality should
not involve tampering with existing files if possible.  I don't want to
check every unfinished change into a branch of its own (which I have to
merge at some point of time) if it can be placed into a file of its own.

David Kastrup

reply via email to

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