Hi list,

I am watching the guile-2-threads grow and really do appreciate that! Many thanks to Antonio, Harm, David, Federico, et al for allyour efforts on this!

There is a another question I have in mind: What would it mean to create LilyDev as a container-based-solution? On my laptop and my working machine I regularly use LXC to start Apache or Tomcat inside a container for testing purposes. And if I have to test something I often do that inside a container (https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/).

Is there a script, which prepares an ubuntu installation for lilydev (beside apt-get build-dep lilypond) and gub? That way one can set up a container, run the setup-script (prob. with options to select either guile 1.8 or 2.0.12/13). The lilydev-solution is just an iso to download. But if you want to test with different guile-versions, you have to provide a vm for each one of them. Containers are much lighter and smaller and use less cpu and take the memory they need - not a fixed amount in the vm-settings.

Summary: Which steps/tasks need to be performed by a setup script to prepare a ubuntu-based installation for lilypond-development and gub (using the local lilypond-sources)? I say ubuntu-based as lilydev is based on it. But other distributions might as well work.

Jan-Peter

Am 24.11.2016 um 07:02 schrieb Paul:
On 11/23/2016 06:09 PM, Thomas Morley wrote:

Currently it seems I'm the only one being able to test Antonio's patches.

This is not exactly optimal.
[...]
Having a LilyDev with guile 2.0.12/13 may help.

I for one would be more likely to help with testing if there were a LilyDev with guile 2.0.12/13

Thanks Antonio, Harm, David, Federico, et al, for your work on this.

-Paul

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to