Development or stable version?
After recently asking about the use of \repeat inside \parallelMusic I was recommended to download to the latest "development" version of Lilypond. At the time I said I wouldn't do this, but would wait for the next "stable" version. But shortly afterwards, I realised that I needed to use \alternative after a repeat. With the version I was using, 2.18.0, this was going to be a nightmare or perhaps impossible, whereas I had already been shown that in a later version it was easy to make things work. So I decided to "bite the bullet", and downloaded and installed the latest version, 2.19.24. I then used convert-ly to update the files I was working on. Result? A very satisfied user! The result has been an overwhelming success, and has saved me a lot of messing about trying to get things working in 2.18.0 which have already been immeasurably improved in later versions of Lilypond. Why am I writing this? Simply to encourage any other user who might benefit from using a later version than the "stable" one. Of course there is the possibility that some as yet unnoticed bug might rear its head at some point, but let's face it, even release issues of most software have the odd bug somewhere. It is that word "unstable" that put me off! Now that I have used 2.19.24 and entered another 30-odd pages of string quartet with no problems, I shall be less chicken-hearted about using development versions in future. David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development or stable version?
Am 10.09.2015 um 16:16 schrieb Kieren MacMillan: > Hi David, > > Welcome to the bleeding edge! =) > > As someone who only uses the “latest” development version(s), and that for > mission-critical daily composition and engraving (i.e., my career), I can say > that the latest “unstable” version is almost always good to go. > > That being said, I do recommend keeping your most recent “stable unstable” > version around at all times, in case you run into a show-stopper bug. A > couple of times in the past five years or so, I had to stay with a version 1 > or 2 behind the absolute latest, in order to get my scores out the door. > Right now, for example, I have .26 (which, so far, I’m using without issue) > and .25 on hand. 'unstable' is something completely different when talking about a CLI compiler than with a GUI program that can crash under you with unsaved files open. I think what is most 'unstable' with the development versions is the language. That is, if you are using any new stuff you have to expect that the syntax changes. While this is not much of a problem for most users (thanks to convert-ly) it is something to consider when you provide some kind of 'public' service, or when you develop an editing program (for example Frescobaldi's syntax knowledge usually refers to the latest stable version - it wouldn't really be appropriate to chase behind unstable syntax changes). I'm also nearly exclusively using development versions. Usually I have a 'fairly recent' binary around and otherwise use a self-compiled version from the latest git repository. Urs > > Cheers, > Kieren. > > > Kieren MacMillan, composer > ‣ website: www.kierenmacmillan.info > ‣ email: i...@kierenmacmillan.info > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development or stable version?
Hi David, Welcome to the bleeding edge! =) As someone who only uses the “latest” development version(s), and that for mission-critical daily composition and engraving (i.e., my career), I can say that the latest “unstable” version is almost always good to go. That being said, I do recommend keeping your most recent “stable unstable” version around at all times, in case you run into a show-stopper bug. A couple of times in the past five years or so, I had to stay with a version 1 or 2 behind the absolute latest, in order to get my scores out the door. Right now, for example, I have .26 (which, so far, I’m using without issue) and .25 on hand. Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development and Stable version on Mac
I assume that this works the same (or at least reasonably similar) on Linux and Mac: - install one version (as you have) on the user level (i.e. not as root) - *move* the whole installation directory from ~/lilypond to somewhere else, e.g. ~/lilyponds/2.18.2 (the last part is an arbitrary name, but I think the version number is a good idea). [arbitrary step to check: - create a symlink from ~/lilypond to the new location ] -install the second version in the user's home directory (the first version has been moved out of the way) - move the new installation directoryy from ~/lilypond to e.g. ~/lilyponds/2.19.16 Now you can set a symlink to point from ~/lilypond to either of the directories where you moved the install dirs to. This way you can easily switch between the two versions. Instead of juggling wiht the symlink you could also create two wrapper scripts that simply call the right executable. I don't know if that works out exactly the same on Mac, but I think the general idea should work. If you are using Frescobaldi, you can simply register an arbitrary number of LilyPond versions in the Preferences, though. HTH Urs Am 31.10.2014 20:19, schrieb Br. Samuel Springuel: What's the simplest way to get both the development and stable version of lilypond running on a Mac from a user perspective? I already have the stable version installed from the downloadable binaries and don't want to mess with this but also want to test some changes that have taken place in the development version to see if they solve some issues I've been having (some chatter on the list makes me think they might). I'm not planning on contributing modifications to the source as I'm too busy with other projects. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development and Stable version on Mac
Am 31.10.2014 20:19, schrieb Br. Samuel Springuel: What's the simplest way to get both the development and stable version of lilypond running on a Mac from a user perspective? I already have the stable version installed from the downloadable binaries and don't want to mess with this but also want to test some changes that have taken place in the development version to see if they solve some issues I've been having (some chatter on the list makes me think they might). I'm not planning on contributing modifications to the source as I'm too busy with other projects. I'd say the easiest way to do this is using homebrew (brew.sh). You can install both regular and devel branches of lilypond (brew install lilypond or brew install --devel lilypond), each in its own directory. Then, you can either use them in its own directory or use brew switch lilypond version to create the correct symlinks automatically. I don't use the devel branch, so I cannot tell you if whether it's broken or not, but it's so easy it's worth a try. ;) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development and Stable version on Mac
2014-10-31 21:43 GMT+01:00 Br. Samuel Springuel rpspring...@gmail.com: 1) Download the binary for the latest development release 2) Unpack the tarball 3) Rename the application file to LilyPond-dev 4) Copy into Applications This is what I usually do. Indeed at the moment I have about a dozen of different versions of LilyPond.app that I renamed as LilyPond X.Y.Z.app (all of them are registered in Frescobaldi). If I remember correctly, this was somehow problematic with 2.12.X and/or 2.13.X, but I think that renaming LilyPond.app version = 2.14.0 is perfectly OK. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Development and Stable version on Mac
What's the simplest way to get both the development and stable version of lilypond running on a Mac from a user perspective? I already have the stable version installed from the downloadable binaries and don't want to mess with this but also want to test some changes that have taken place in the development version to see if they solve some issues I've been having (some chatter on the list makes me think they might). I'm not planning on contributing modifications to the source as I'm too busy with other projects. -- ✝ Br. Samuel, OSB (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Development and Stable version on Mac
Figured out the answer to my own question: 1) Download the binary for the latest development release 2) Unpack the tarball 3) Rename the application file to LilyPond-dev 4) Copy into Applications 5) Create command line alias scripts which point to the development version -- ✝ Br. Samuel, OSB (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
