Le 01/01/2014 20:45, James disait :
On 01/01/14 17:50, Jean-Charles Malahieude wrote:
I compile on native Fedora. I don't know by how would be multiplied a
90 minutes "make -j3 && make -j3 doc" on my dual-core with 2gigs RAM
when launched in a VM.
Probably not as much as you think. Assuming you have reasonably modern
CPUs with VT-x/d enabled. It's very convenient to use a VM than your own
base system, but it does take disk space I guess (for the extra OS). You
also get trivial abilities to clone/snapshot and/or freeze VMs that I
have found helpful in the past. Indeed before Patchy scripts it was how
I used to test patches without having to keep rebuilding a baseline
image for the reg test comparisons.
My box is now 7 years old and doesn't seem to accept VT-x/d. It is not a
problem of space but of resources. I work in local clones with
git clone -l -s -n --branch translation . ../Traduc
However, how often are you building full doc? And why - when we have
others who do this. We have scripts don't we that allow you to build
*just* sections or *just* languages instead of everything. It's not like
it's mandatory for most, if hardly any, developers. […]
I consider it mandatory for translators to build from scratch when
updating multiple files, before pushing on the translation branch.
Here is my work-flow:
1- update the text and add new texidocs when needed,
2- make -j3 doc LANGS="fr" (less than 10 min.)
3- check the logs and proofread in a browser (more fluent reading than
source file)
4- commit and push
Cheers,
Jean-Charles
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
