Re: better LSR to lilypond snippet conversion tool

[Dan Eble]

On Oct 8, 2019, at 16:21, Werner LEMBERG  wrote:
> I'm not sure how to proceed.  Shall I adapt `makelsr.py' to start
> where this script stops?

I can't contribute much to an answer, but I want to say that the last time I 
tried updating snippets (probably over a year ago), the documented process 
failed because my source tree is read-only in my build environment and the 
script tries to rewrite source files.

I’ve been expecting to have to do one of the following (from most to least 
preferred) in order to make it work for me.

1. Add an option to create snippets in the build directory and stop.  Copy them 
to the source directory manually in the host environment.

2. Grant my build environment write access to the source directory when I want 
to import snippets.

3. Never run the script.  Ask others to do it.

4. Run the script in the host environment.

I humbly request that as you are working on this process, you try to avoid 
making (1) more difficult.

Regards,
— 
Dan


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

Re: LSR inconsistencies

[Thomas Morley]

Am Mo., 7. Okt. 2019 um 09:16 Uhr schrieb Werner LEMBERG :
>
>
> > #1033 can be found in the 2.19.83-snippets, but not in master. No
> >   clue.
> > #1069 was approved Thursday or Friday, can't be in the source until
> >   someone does a lsr-import
> > #1071 same as for #1069
>
> OK.  Thanks for checking.
>
> > #1083 title corrected, no clue why it's missing in master
>
> I don't see a corrected title in today's sqldump file.  [And in the
> text body the word is written incorrectly, too.]

Maybe I forgot to actually _store_ it :((
Hopefully it'll works now.

>
> Another minor issue: There are some snippets that have a full stop at
> the end of the title.  IMHO, a title should never have that.
>
>   http://lsr.di.unimi.it/LSR/Item?id=310
>   http://lsr.di.unimi.it/LSR/Item?id=336
>   http://lsr.di.unimi.it/LSR/Item?id=737
>   http://lsr.di.unimi.it/LSR/Item?id=775
>   http://lsr.di.unimi.it/LSR/Item?id=857
>   http://lsr.di.unimi.it/LSR/Item?id=1097

I'll have a look soon.

Cheers,
  Harm

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

Re: lilypond does not work with Mac OS 10.15 (Catalina)

[Hans Åberg]

> On 8 Oct 2019, at 09:57, Maria-Angeles Casares-de-Cal via lilypond-devel 
>  wrote:
> 
> For the attention of the Lilypond Developer Team:
> 
> Lilypond is an remarkable app, but now Lilypond does not work with the new 
> Mac operating system (macOS 10.15 Catalina).
> 
> Will we have news soon of the new Lilypond (64 bits) to work in macOS 10.15?

It seems that the MacPorts version can be run if installed before the MacOS 
update. It cannot be updated, though, but hopefully a new MacPorts version will 
come soon enough.

Specifically:

First install MacPorts on MacOS 10.14. See their site for instructions. Then run
  sudo port install lilypond-devel
When checking that it works, update to MacOS 10.16. After that, the new default 
shell is zsh, so copy .bashrc to .zshrc, and hopefully the shells are 
compatible enough for that to work.


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

Re: macOS 64-bit

[Marnen Laibow-Koser]

On Mon, Jul 8, 2019 at 11:16 AM Marnen Laibow-Koser 
wrote:

>
>
> On Mon, Jul 8, 2019 at 11:14 AM Werner LEMBERG  wrote:
>
>>
>> >> You mean a stand-alone package that can be easily distributed,
>> >> right?  Since MacPorts does provide a 64bit version with the
>> >> `lilypond-devel' package.
>> >
>> > Yes, thanks for the correction.  The easiest way right now will
>> > probably be with port mdmg, but I want to see if I can do better.
>>
>> I think that the resulting bundle size of the `port mdmg' command can
>> be greatly reduced if you improve the lilypond-devel package
>> dependencies (i.e., adjusting the packages needed for building and
>> running).  Unfortunately, I don't have enough time right now to do it
>> by myself; additionally, I'm not a MacOS user at all :-)
>
>
> Right, you mentioned that earlier.  Additionally, I want to see what
> happens if I do a non-MacPorts build.  The MacStadium environment that we
> now have access to will let me play around with this without cluttering up
> my own Mac with a lot of crap (although I *could* run a VM locally...).
>

Update: with wedding stuff, I haven’t had time to devote to this, but with
Mac OS Catalina coming out this has become more urgent, as Catalina removes
32-bit support altogether.  I’m gonna try to spend some time on this in the
next few days, and would welcome help from anyone interested.  I’ll post
info for the MacStadium environment once I set it up.

Best,
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypond does not work with Mac OS 10.15 (Catalina)

[Dan Eble]

On Oct 8, 2019, at 11:09, Carl Sorensen  wrote:
> Federico Bruno says the latest LilyDev includes a Docker container. 
> http://lilypond.1069038.n5.nabble.com/LilyDev-0-3-released-td217945.html 
> 


FYI, I’m working on extending that to provide a separate container in which to 
run lilypond after it has been built from source, which maps the user’s 
LilyPond scores and host fonts into the container.  This will make it easier 
for contributors who are macOS users to test their own scores before posting 
changes for review.

This is not intended to satisfy “normal” users, but it will be a part of my own 
composing workflow until another solution is available.
— 
Dan

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

Re: lilypond does not work with Mac OS 10.15 (Catalina)

[Carl Sorensen]

On 10/8/19, 7:34 AM, "lilypond-devel on behalf of Karlin High" 
 wrote:

On 10/8/2019 2:57 AM, Maria-Angeles Casares-de-Cal via lilypond-devel wrote:
> Will we have news soon of the new Lilypond (64 bits) to work in macOS 
10.15?
> 
> We hope you can solve this issue. It is worth the work of updating 
Lilypond so that it can be used from now on the new Apple computers and the old 
ones that have been updated to the new operating system.

Unfortunately, there is currently no clear path to making a 64-bit macOS 
distribution of LilyPond. There is a conflict between Apple's Software 
License Agreement for their XCode developer tools and the GNU General 
Public License that LilyPond uses. This has been discussed at length 
elsewhere on LilyPond email lists, references can be given if they'd be 
helpful for you.

There are three options available to you:

1) Build your own LilyPond using MacPorts:  
http://lilypond.1069038.n5.nabble.com/LilyPond-64-bit-version-for-a-Mac-td220488.html#a220492
It sounds like this is a pretty straightforward process, once you have 
downloaded Xcode from Apple.

2) Install  a virtual machine running linux: https://www.virtualbox.org/  and 
install a linux version of LilyPond in the virtual machine.

3) Run lilypond in a Docker container: 
https://blog.stephencleary.com/2018/05/docker-as-a-tool-provider.html
I have no experience with Docker, so I can't speak to this personally, but a 
number of people have talked about using Docker on the lists.

Federico Bruno says the latest LilyDev includes a Docker container. 
http://lilypond.1069038.n5.nabble.com/LilyDev-0-3-released-td217945.html

I hope you can do one of these.

Thanks,

Carl



 

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

Re: lilypond does not work with Mac OS 10.15 (Catalina)

[Karlin High]

On 10/8/2019 2:57 AM, Maria-Angeles Casares-de-Cal via lilypond-devel wrote:

Will we have news soon of the new Lilypond (64 bits) to work in macOS 10.15?

We hope you can solve this issue. It is worth the work of updating Lilypond so 
that it can be used from now on the new Apple computers and the old ones that 
have been updated to the new operating system.


Unfortunately, there is currently no clear path to making a 64-bit macOS 
distribution of LilyPond. There is a conflict between Apple's Software 
License Agreement for their XCode developer tools and the GNU General 
Public License that LilyPond uses. This has been discussed at length 
elsewhere on LilyPond email lists, references can be given if they'd be 
helpful for you.

--
Karlin High
Missouri, USA

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

lilypond does not work with Mac OS 10.15 (Catalina)

[Maria-Angeles Casares-de-Cal via lilypond-devel]

For the attention of the Lilypond Developer Team:

Lilypond is an remarkable app, but now Lilypond does not work with the new Mac 
operating system (macOS 10.15 Catalina).

Will we have news soon of the new Lilypond (64 bits) to work in macOS 10.15?

We hope you can solve this issue. It is worth the work of updating Lilypond so 
that it can be used from now on the new Apple computers and the old ones that 
have been updated to the new operating system.

Thank you very much for the work you do and for giving us the opportunity to 
use this outstanding app that allows us to write music and make scores with 
extraordinary quality.

Sincerely,

Ángeles Casares
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: PATCHES - Countdown for October 8th

[Dan Eble]

Issue 5564 is being neglected.  I need some help understanding how to reproduce 
the test failures.
https://sourceforge.net/p/testlilyissues/issues/5564/ 

— 
Dan

> On Oct 8, 2019, at 07:05, James Lowe  wrote:
> 
> Hello,
> 
> Here is the current patch countdown list. The next countdown will be on
> October 10th.
> 
> 
> A quick synopsis of all patches currently in the review process can be
> found here:
> 
> http://philholmes.net/lilypond/allura/
> 
> 
> 
> 
> Push:
> 
> 5566 Update python headers to match surrounding files - masterodin
> https://sourceforge.net/p/testlilyissues/issues/5566
> http://codereview.appspot.com/565080043
> 
> 5565 simplify python-related makefiles - Dan Eble
> https://sourceforge.net/p/testlilyissues/issues/5565
> http://codereview.appspot.com/581080044
> 
> 5559 Add user-definable ottavation markups - Malte Meyn
> https://sourceforge.net/p/testlilyissues/issues/5559
> http://codereview.appspot.com/568970043
> 
> 
> Countdown:
> 
> 5568 Make build output terse by default - Dan Eble
> https://sourceforge.net/p/testlilyissues/issues/5568
> http://codereview.appspot.com/557080043
> 
> 
> Review:
> 
> 5570 Fix header variables from musicxml2ly on Windows - hahnjo
> https://sourceforge.net/p/testlilyissues/issues/5570
> http://codereview.appspot.com/545040043
> 
> 5569 Drop requirement for python-devel - hahnjo
> https://sourceforge.net/p/testlilyissues/issues/5569
> http://codereview.appspot.com/566870043
> 
> 
> New:
> 
> 5567 Allow slurs instead of brackets with tuplets - Werner LEMBERG
> https://sourceforge.net/p/testlilyissues/issues/5567
> http://codereview.appspot.com/581110043
> 
> 
> ***
> 
> Regards,
> 
> 
> James
> 
> - End Forwarded Message -
> 
> 
> ___
> 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

PATCHES - Countdown for October 8th

[James Lowe]

Hello,

Here is the current patch countdown list. The next countdown will be on
October 10th.


A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/




Push:

5566 Update python headers to match surrounding files - masterodin
https://sourceforge.net/p/testlilyissues/issues/5566
http://codereview.appspot.com/565080043

5565 simplify python-related makefiles - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/5565
http://codereview.appspot.com/581080044

5559 Add user-definable ottavation markups - Malte Meyn
https://sourceforge.net/p/testlilyissues/issues/5559
http://codereview.appspot.com/568970043


Countdown:

5568 Make build output terse by default - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/5568
http://codereview.appspot.com/557080043


Review:

5570 Fix header variables from musicxml2ly on Windows - hahnjo
https://sourceforge.net/p/testlilyissues/issues/5570
http://codereview.appspot.com/545040043

5569 Drop requirement for python-devel - hahnjo
https://sourceforge.net/p/testlilyissues/issues/5569
http://codereview.appspot.com/566870043


New:

5567 Allow slurs instead of brackets with tuplets - Werner LEMBERG
https://sourceforge.net/p/testlilyissues/issues/5567
http://codereview.appspot.com/581110043


***

Regards,


James

- End Forwarded Message -


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