On Fri, Jun 25, 2010 at 02:00:53PM +0200, Mike Solomon wrote: > 1) How would I create a separate branch?
For your local copy of the source, just do it the normal git way. There's lots of git tutorials online. You can't push that branch onto our shared git repo without having git access, though, so you'd probably need to upload it to a temporary github space. > 2) Would it be worth it simply to include glpk in my patch? It requires no > dependencies itself to compile and it is lightweight, so it could become > "part" of lilypond, but I don't know if that's how things roll chez GNU. I'm not really certain about this. How big is the file? We _do_ include texinfo.tex, so there's _some_ precedent for included parts of other projects. > 3) Would it be possible as a middleground of sorts to create an "optional" > dependency in lilypond? That is, look for glpk and compile the waveforms > stuff only if it is found? I figured out a way to write that bit of code in > the configure file if said maneuver is ok. I'm not so fond of this idea, and if we decided to go that route, glpk would need to be added to GUB as well. If it really has no dependencies for compiling and has a typical build system, this wouldn't be too hard, but I can't do it myself until Aug. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
