On 11/25/2016 06:13 PM, Thomas Morley wrote:
- Investigate why lilypond is a lot slower when using guile-2.0
This is the current main problem, I'd say.
From what I've read, the guile 2.0 interpreter is simply slower than
the guile 1.8 interpreter (with the trade-off being that 2.0 has a
com
atches are a moving target we should choose
> one of these two alternative approaches:
>
> 1. Use only one branch, but warn users that the branch might be
> rebased, this would mean that "git pull --force" might be needed on
> the client side.
>
> 2. Use versio
Hi Antonio!
TBH I didn't try to compile lilypond using guile-1.8 with my patches
applied, I can give it a go in the next days.
I added your patches in numerical order as single commits to my local branch on
top
of current master and started a "git bisect run" process to investigate which
of yo
Am 25.11.2016 um 23:19 schrieb Antonio Ospite:
stuff to simplify the workflow, attracting more people.
It's still tedious to add Antonios patches.
How about creating a public branch?
I could do this in the evening (if I remember the syntax)
What do you think?
Shouldn't most of them be able to
On Fri, 25 Nov 2016 13:29:39 +0100
Knut Petersen wrote:
> Hi everybody!
>
> Status of guile on OpenSuSE distributions:
> ==
[...]
> Building current lilypond master + the 15 patches from
> ao2.it/tmp/lilypond-guile2/patches_2016-11-22 using guile 2 on
> Tu
quot; might be needed on
the client side.
2. Use versioned branches, this means that when the need for a rebase
arises the result of the rebasing goes into a new branch, e.g.:
guile-2.0-v2
or
guile-2.0-20161125
In the mean time I started to write a TODO list of the
I've just seen an error in my first email. This is correct:
debootstrap --arch=amd64 stretch DebianStretch
http://httpredir.debian.org/debian/
sudo systemd-nspawn -D DebianStretch
of course you can replace DebianStretch with whatever directory name
you prefer
___
Jan-Peter Voigt:
> Am 24.11.2016 um 16:10 schrieb Antonio Ospite:
> > And about the choice between guile 1.8 or 2.0.12/13, it should be
> > possible to have both guile-1.8 and guile-2.0 packages installed in the
> > same image and then let lilypond choose which one to pick up at
> > configure-time,
Hi all
For those who want to contribute to the guile-2 migration, I suggest
you use a Linux container, because I'm having troubles with building a
new LilyDev image and I don't know when I'll find a solution.
I quickly wrote a brief tutorial to set up a Debian or Fedora guest
within a system
Hi everybody!
Status of guile on OpenSuSE distributions:
==
OpenSuSE Tumbleweed includes guile 2.0.13 since 2016-10-15.
OpenSuSE Leap does include guile 2, but the version is too old to support
lilypond.
Manual installation of the guile 2 version from Tum
David Kastrup writes:
> Thomas Morley writes:
>
>> 2016-11-24 16:10 GMT+01:00 Antonio Ospite :
>>> On Thu, 24 Nov 2016 14:03:32 +0100
>>> Federico Bruni wrote:
>>
>>
>>
>> Hi all,
>>
>> with the container and/or LilyDev for guile2 we are going to have some
>> stuff to simplify the workflow, att
Thomas Morley writes:
> 2016-11-24 16:10 GMT+01:00 Antonio Ospite :
>> On Thu, 24 Nov 2016 14:03:32 +0100
>> Federico Bruni wrote:
>
>
>
> Hi all,
>
> with the container and/or LilyDev for guile2 we are going to have some
> stuff to simplify the workflow, attracting more people.
> It's still ted
2016-11-24 16:10 GMT+01:00 Antonio Ospite :
> On Thu, 24 Nov 2016 14:03:32 +0100
> Federico Bruni wrote:
Hi all,
with the container and/or LilyDev for guile2 we are going to have some
stuff to simplify the workflow, attracting more people.
It's still tedious to add Antonios patches.
How about
13 matches
Mail list logo
