Re: state of the ’Pond for earnest tadpoles

On 03/01/2021 10:07, James wrote: my desktop before that was from 2013 (i5 something) and I was getting sub hour make doc times even then but using 3 CPUs. So you having those timings while using a -j5 option ... wow! I am obviously inhabiting some technological bubble that I wasn't aware I w

Re: state of the ’Pond for earnest tadpoles

Hello On 02/01/2021 16:58, Thomas Morley wrote: Am Sa., 2. Jan. 2021 um 14:41 Uhr schrieb James : On 02/01/2021 12:20, Thomas Morley wrote: A full `make doc` takes hours for me, even if invoked with `make doc -j5 CPU_COUNT=5` Thus I hardly do so, but use the CG-documented methods: Hours? Re

Re: state of the ’Pond for earnest tadpoles

Am Sa., 2. Jan. 2021 um 14:41 Uhr schrieb James : > > > On 02/01/2021 12:20, Thomas Morley wrote: > > A full `make doc` takes hours for me, even if invoked with `make doc > > -j5 CPU_COUNT=5` > > Thus I hardly do so, but use the CG-documented methods: > > Hours? > > Really? > > Perhaps 'an hour' if

Re: state of the ’Pond for earnest tadpoles

On 02/01/2021 15:38, Kieren MacMillan wrote: I’m using an 11-year old iMac, running LilyDev in a Linux VM. =) Oh .. OK. Yeah. Don't make doc. %^) James

Re: state of the ’Pond for earnest tadpoles

Hi all, >> Perhaps 'an hour' if you were using some very, very old CPU - but even using >> a single CPU on an 'old' i5 Intel system a full make doc for me took less >> than 50 mins. That last time it took longer than an hour was when I had an >> old (8+ years ago) iMac running make doc in a lin

Re: state of the ’Pond for earnest tadpoles

Hello On 02/01/2021 14:07, Trevor wrote: James wrote 02/01/2021 13:41:06 On 02/01/2021 12:20, Thomas Morley wrote: A full `make doc` takes hours for me, even if invoked with `make doc -j5 CPU_COUNT=5` Thus I hardly do so, but use the CG-documented methods: Hours? Really? Perhaps 'an hour' i

Re[2]: state of the ’Pond for earnest tadpoles

James wrote 02/01/2021 13:41:06 On 02/01/2021 12:20, Thomas Morley wrote: A full `make doc` takes hours for me, even if invoked with `make doc -j5 CPU_COUNT=5` Thus I hardly do so, but use the CG-documented methods: Hours? Really? Perhaps 'an hour' if you were using some very, very old CP

Re: state of the ’Pond for earnest tadpoles

On 02/01/2021 12:20, Thomas Morley wrote: A full `make doc` takes hours for me, even if invoked with `make doc -j5 CPU_COUNT=5` Thus I hardly do so, but use the CG-documented methods: Hours? Really? Perhaps 'an hour' if you were using some very, very old CPU - but even using a single CPU o

Re: state of the ’Pond for earnest tadpoles

Am Sa., 2. Jan. 2021 um 13:20 Uhr schrieb Thomas Morley : > > Hi Kieren, > > Am Sa., 2. Jan. 2021 um 00:00 Uhr schrieb Kieren MacMillan > : > > > > Hi Michael (et al.), > > > > > please use http://lilypond.org/doc/v2.21/Documentation/contributor/lilydev > > > instead. I adjusted some parts of this

Re: state of the ’Pond for earnest tadpoles

Hi Kieren, Am Sa., 2. Jan. 2021 um 00:00 Uhr schrieb Kieren MacMillan : > > Hi Michael (et al.), > > > please use http://lilypond.org/doc/v2.21/Documentation/contributor/lilydev > > instead. I adjusted some parts of this section last year. However, I > > would be happy to hear if something remains

Re: state of the ’Pond for earnest tadpoles

It shouldn't take multiple hours unless your system is very slow.  A few 10s of minutes is a more reasonable expectation. On 01/01/2021 23:00, Kieren MacMillan wrote: Hi Michael (et al.), please use http://lilypond.org/doc/v2.21/Documentation/contributor/lilydev instead. I adjusted some part

Re: state of the ’Pond for earnest tadpoles

Hi Michael (et al.), > please use http://lilypond.org/doc/v2.21/Documentation/contributor/lilydev > instead. I adjusted some parts of this section last year. However, I > would be happy to hear if something remains still unclear. This is great. Thanks. I have now compiled Lilypond on my machine!

Re: state of the ’Pond for earnest tadpoles

Hi Kieren, Hi Jonas (et al.), I would claim that the contributor experience has been pretty stable since the initial switch to GitLab. Enabling CI and the recent work to also run 'make check' automatically shouldn't change much from a contributor's point of view, I hope. I can't promise to gi

Re: state of the ’Pond for earnest tadpoles

Il giorno ven, gen 1 2021 at 16:37:40 -0500, Kieren MacMillan ha scritto: Hi Jonas (et al.), I would claim that the contributor experience has been pretty stable since the initial switch to GitLab. Enabling CI and the recent work to also run 'make check' automatically shouldn't change

Re: state of the ’Pond for earnest tadpoles

Hi Jonas (et al.), > I would claim that the contributor experience has been pretty stable > since the initial switch to GitLab. Enabling CI and the recent work to > also run 'make check' automatically shouldn't change much from a > contributor's point of view, I hope. > I can't promise to give det

Re: state of the ’Pond for earnest tadpoles

Hi Kieren, I would claim that the contributor experience has been pretty stable since the initial switch to GitLab. Enabling CI and the recent work to also run 'make check' automatically shouldn't change much from a contributor's point of view, I hope. I can't promise to give detailed guidance, th

state of the ’Pond for earnest tadpoles

Hello all! I’m just wondering if the new process / repo / workflow is in a state where an enthusiastic but oft-discouraged[-by-the-state-of-the-tech-and-process] Frog might finally dive in fully to the contribution process? If so, which Jedi Master(s) might patiently guide this young Padawan th