definitive git instructions

2008-12-26 Thread Graham Percival
We have a bunch of different "getting started with git" instructions floating around. The main "development" page talks about git clone; GDP suggested "git init; git remote add...; git checkout"; the README in web/ (and now web-gop/) branches talks about "git init-db; ... set up .git/remotes/...;

Re: creating dev/gop-web

2008-12-26 Thread Graham Percival
We can take this public now... On Sat, Dec 27, 2008 at 01:43:35AM +0100, John Mandereau wrote: > Le vendredi 26 d??cembre 2008 ?? 14:25 -0800, Graham Percival a ??crit : > > Could one of you kind git-savvy people please create a branch > > containing the attached (untarred) files? > > Let's name

GOP website; please add tasks

2008-12-26 Thread Graham Percival
I have the initial GOP website up now: http://percival-music.ca/gop/ If I've missed any ongoing or temporary jobs that we'd like filled, please let me know. I'm planning on sending the first round of pleas out to -user in a few days. I'm not including jobs that are single-person and clearly def

Re: GOP: new website

2008-12-26 Thread John Mandereau
Le jeudi 25 décembre 2008 à 21:03 -0800, Graham Percival a écrit : > I'm trying to decide how to build the new website. In particular, > I'd like to be able to create pdfs as well as the html. Good idea! > I currently see four options: > 1) Build the website with texinfo and texi2html. With s

Re: GOP: new website

2008-12-26 Thread Patrick McCarty
On Fri, Dec 26, 2008 at 8:02 AM, Valentin Villenave wrote: > 2008/12/26 Carl Sorensen : > >> #4 seems good to me. No need to make the website in pdf form. > > If I may add my 2 geeky cents, if we used a PHP-based content > management system, we could easily offer a PDF version of the website > fo

Re: GOP: new website

2008-12-26 Thread Werner LEMBERG
> > Seriously, I think that parts of the LM and AU could appear on the > > website in html generated from the same source as in the manuals, > > but with different links. > > > > I think there needs to be only one *source* for information, but > > not necessarily only one representation. > > Wel

Re: GOP: new website

2008-12-26 Thread Graham Percival
On Fri, Dec 26, 2008 at 05:02:01PM +0100, Valentin Villenave wrote: > 2008/12/26 Carl Sorensen : > > > #4 seems good to me. No need to make the website in pdf form. > > If I may add my 2 geeky cents, if we used a PHP-based content > management system, PHP... that's the scripting language that h

Re: GOP: new website

2008-12-26 Thread Graham Percival
On Fri, Dec 26, 2008 at 08:16:07AM -0700, Carl D. Sorensen wrote: > > Seriously, I think that parts of the LM and AU could appear on the website > in html generated from the same source as in the manuals, but with different > links. > > I think there needs to be only one *source* for information,

Re: GOP: new website

2008-12-26 Thread Valentin Villenave
2008/12/26 Carl Sorensen : > #4 seems good to me. No need to make the website in pdf form. If I may add my 2 geeky cents, if we used a PHP-based content management system, we could easily offer a PDF version of the website for download, through an existing plugin (there are PDF plugins for Drupa

Re: Are tick barlines too thin?

2008-12-26 Thread Neil Puttock
2008/12/25 Carl Sorensen : > Sounds like ticks should be some fraction of the standard barline > thickness, instead of the staff line thickness. That way, the override > would apply to barline, instead of staff lines. I agree; either using a set fraction of 'hair-thickness or by introducing a ne

Re: GOP: new website

2008-12-26 Thread Carl D. Sorensen
On 12/25/08 10:24 PM, "Graham Percival" wrote: > On Fri, Dec 26, 2008 at 05:18:50AM +, Carl Sorensen wrote: >> Graham Percival percival-music.ca> writes: >> >>> 4) Abandon the "complete website as pdf" idea and just give >>> people a tarball of the website for off-online browsing. >> >

`programming error' for --disable-optimisation

2008-12-26 Thread Werner LEMBERG
If compiled with --disable-optimisation, calling lilypond always emits programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers programming error: Parsed object should be dead: static scm_unused_struct*