Re: Improving the Contributors Guide and LilyDev

[Urs Liska]

Am 06.05.2015 um 07:34 schrieb Federico Bruni:
> 2015-05-06 7:19 GMT+02:00 Janek Warchoł <address@hidden>:
>
> > as I've already mentioned, I've already started working on a new
> > LilyDev.  I'm going to use tools that should make it easy to build
> > different versions of LilyDev (e.g. 32-bit and 64-bit, possibly also
> > based on different distros).
> I though that you had some ideas on how to improve LilyDev, not that you
> were working on building a new LilyDev..
>
>
> > In order to reduce work duplication, I suggest to wait with further
> > discussion until I have a working "prototype", which I'll present to
> > you for evaluation.  Hopefully this will happen within a week from
> > now.
> I started updating LilyDev yesterday but spent just 20 minutes.
> I invested some time last year to get started, but live-build is quite easy
> to update and maintain.
>
> I'll wait for your prototype, even if it looks like a work duplication
> already.
> Why not improving what's already available? Which advantages have the tools
> you are using?
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

As a side note: What would be the amount of work to provide a lily-dev 
metapackage that could be used by people who are already using a Linux 
distribution? As a Linux user I would prefer modifying my own system 
over using a precompiled LilyDev distro in a VM. I recall that setting 
up my systems on different machines (several different Debian based 
distros, including my "virtual private" web server) was actually quite 
simple. The only real issue I had (and still have) is through the fact 
that I have a manual TeXLive installation that doesn't really go well 
with LilyPond trying to access the packaged version.
I think this is more or less a case of installing a number of packages 
through apt, cloning a number of repositories and adding a number of 
paths to .bashrc.

I will soon have the opportunity to test that on a computer that I'll 
install from scratch. That way I can at least write step-by-step 
directions to get a Debian computer to work with LilyPond development. 
But maybe it would also be good to have an even more streamlined approach?
(OTOH, what I did was actually reading Janek's script and perform its 
steps manually, with more control. So maybe it would also be a good idea 
to build upon that script and make it perhaps somewhat more generic, 
with more configuration options?)

Urs