Re: Windows Releases (patch included)
J L escreveu: > Hi, > > Following a little bit of investigation, the changes I propose are given > below. Sorry, I couldn't get a diff off git (no git installed here, and > installing might be troublesome), so my 'hack' will be presented at the > end of this mail. > > All this really does, is it makes 'registering the lilypond-python as > the default python' optional. By default, it should still be on, so no > problems for people who just want working lilypond install. I'm guessing > that this should work, but there is a chance it might not. thanks. Applied. Expect it in .20 -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
J L escreveu: > Anyways, I'll be looking into adding some sort of way to make the > registry entries for python-interpreter becoming optional (of course, it > will be on by default, for all the windows users who wouldn't know > better). I'm guessing that the file that the installer is build from is > called lilypond.nsi in the GUB/nsis/ directory (or whatever it's called > in git). There was a git.nsi file there as well, so I'm not sure which > one it is. It's lilypond.nsi. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases (patch included)
Hi, Following a little bit of investigation, the changes I propose are given below. Sorry, I couldn't get a diff off git (no git installed here, and installing might be troublesome), so my 'hack' will be presented at the end of this mail. All this really does, is it makes 'registering the lilypond-python as the default python' optional. By default, it should still be on, so no problems for people who just want working lilypond install. I'm guessing that this should work, but there is a chance it might not. Regards, Joshua Leung -- $File: GUB head -> nsis/lilypond.nsi $Line 106 (remove that line): Call registry_python $Line 121 (add following lines): ;; Optional section (can be disabled by the user) Section "Bundled Python" ;; Only make bundled python interpreter the default ;; if user wants it to be (i.e. for the average windows ;; user who only cares that software works just like that) Call registry_python SectionEnd _ Find the coolest online games @ http://xtramsn.co.nz/gaming ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Hi, There are actually two major problems with what the installer is currently doing: 1) It used to add the lilypond path near the start of the PATH variable (but I think that has been changed to be at the end at one point?) 2) It forces all python scripts to be run with the python bundled with lilypond. This is OK if you don't have any other (native) install of python on your computer, but it does cause problems if you do. Apart from problems related to modules not being found, it also breaks scripts that are dependant on features only available in a version newer than the installed one. 3) It removes all existing entries from the right-click context menu for python-scripts that were there by default. I'm not so worried about the bundled scripts not running for me, as about breaking the stable setup I use for everything else (namely developing/using some of my own scripts, building other open-source projects I'm involved with). Anyways, I'll be looking into adding some sort of way to make the registry entries for python-interpreter becoming optional (of course, it will be on by default, for all the windows users who wouldn't know better). I'm guessing that the file that the installer is build from is called lilypond.nsi in the GUB/nsis/ directory (or whatever it's called in git). There was a git.nsi file there as well, so I'm not sure which one it is. Regards, J. Leung From: Mats Bengtsson <[EMAIL PROTECTED]> To: J L <[EMAIL PROTECTED]> CC: lilypond-devel@gnu.org Subject: Re: Windows Releases Date: Tue, 20 Feb 2007 13:32:48 +0100 MIME-Version: 1.0 Received: from iris.s3.kth.se ([130.237.43.24]) by bay0-mc1-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, 20 Feb 2007 04:32:50 -0800 Received: from localhost (radien.md.kth.se [130.237.57.166])by localhost.md.kth.se (Postfix) with ESMTP id 779AB61A9C;Tue, 20 Feb 2007 13:32:49 +0100 (CET) Received: from iris.s3.kth.se ([130.237.43.24]) by localhost (radien.md.kth.se [130.237.57.166]) (amavisd-new, port 10027) with ESMTP id 03961-05; Tue, 20 Feb 2007 13:32:48 +0100 (CET) Received: from iris.s3.kth.se (radien.md.kth.se [130.237.57.166])by localhost.s3.kth.se (Postfix) with ESMTP id 6C10C61AA1;Tue, 20 Feb 2007 13:32:48 +0100 (CET) Received: from [130.237.50.49] (drongo.s3.kth.se [130.237.50.49])by iris.s3.kth.se (Postfix) with ESMTP id 2277161A9C;Tue, 20 Feb 2007 13:32:48 +0100 (CET) X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK3oXsmRrh6gU= User-Agent: Thunderbird 1.5.0.9 (X11/20061206) References: <[EMAIL PROTECTED]> Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 20 Feb 2007 12:32:50.0706 (UTC) FILETIME=[3C2E3F20:01C754EB] As has already been stated. the Python bundled with LilyPond is sufficiently functional to handle all the Python scripts such as midi2ly, convert-ly, lilypond-book, ... If you find any problem with any of these scripts, please send a bug report. I guess your real problem is that you have installed the native Python for Windows package from www.python.org and that LilyPond adds its own bin\ folder in front of that in the PATH. A solution to that would be add wrapper scripts around all these, just as is done in the LilyPond installation package for Linux. I remember that there were some problems with using wrapper BAT scripts in the Windows installation package some years ago, but if those problems only were related to Win98, it might be worth to try a similar approach again. /Mats _ Need more speed? Get Xtra Broadband @ http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Don't talk nonsense! It works perfectly well to run commands like convert-ly -e myfile.ly from the command prompt. Wow, sorry. I never thought that. It seems that I must update my knowledge. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
I was thinking a bit more. Installing and uninstalling LilyPond itself should remain separate from jEdit. So there should be one installer that separately installs the two. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Bertalan Fodor wrote: Putting these into the path would also not help. - you can not run convert-ly.py Don't talk nonsense! It works perfectly well to run commands like convert-ly -e myfile.ly from the command prompt. - you must use python convert-ly.py - But if you do, you must say: python "c:\program files\lilypond\usr\bin\convert-ly.py" So you didn't gain much. No, this used to be the case one year ago, but all these Python problems have been solved at least since version 2.10.0. /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Putting these into the path would also not help. - you can not run convert-ly.py - you must use python convert-ly.py - But if you do, you must say: python "c:\program files\lilypond\usr\bin\convert-ly.py" So you didn't gain much. Still I don't see it is useful. Perhaps we should look at the possibilities of packaging LilyPond with JEdit + Java + LilyPondTool. Actually Java license allows to distribute the runtime with your application, jEdit is GPL. Neither Java, nor jEdit needs anything written to the registry to work, they just can be zipped together. So we could make a directory structure like this: Program Files - LilyPond -- usr -- bin -- java --- bin javaw.exe -- jedit --- jars LilyPondTool.jar Console.jar ... And make a shortcut that runs: c:\Program Files\LilyPond\java\bin\javaw.exe -jar c:\Program Files\LilyPond\jedit\jedit.jar The download size would not be small: LilyPond 18MB jEdit 2MB jEdit plugins 15MB Java runtime 24MB That is 59MB. Bert Since midi2ly, lilypond-book and the other utility scripts are not available via any graphical interface. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Bertalan Fodor wrote: Of course it should, but probably not the current \bin\ folder Why? On Windows platforms people rarely use the PATH to run programs. Since midi2ly, lilypond-book and the other utility scripts are not available via any graphical interface. Of course, your immediate response is that they should install LilyPondTool, but at least as long as LilyPondTool isn't distributed together with LilyPond, the command line interface is the only way to access these functions. I did some experiments recently to try to add a menu option to convert-ly when you right-click on a .ly file, but it seems impossible to use .py scripts as menu actions even though they can be used as commands from the command line. Also, my attempts to make a BAT wrapper failed (don't remember all the details right now). /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Of course it should, but probably not the current \bin\ folder Why? On Windows platforms people rarely use the PATH to run programs. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Of course it should, but probably not the current \bin\ folder but a folder that only contains wrapper scripts to lilypond, lilypond-book, midi2ly, ... which call the real programs from a directory that's not in the PATH. This is the way it's done in the Linux installers. /Mats Bertalan Fodor wrote: I don't think that lilypond path should be in the PATH. Bert -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
I don't think that lilypond path should be in the PATH. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
As has already been stated. the Python bundled with LilyPond is sufficiently functional to handle all the Python scripts such as midi2ly, convert-ly, lilypond-book, ... If you find any problem with any of these scripts, please send a bug report. I guess your real problem is that you have installed the native Python for Windows package from www.python.org and that LilyPond adds its own bin\ folder in front of that in the PATH. A solution to that would be add wrapper scripts around all these, just as is done in the LilyPond installation package for Linux. I remember that there were some problems with using wrapper BAT scripts in the Windows installation package some years ago, but if those problems only were related to Win98, it might be worth to try a similar approach again. /Mats J L wrote: Hi, It's been a while since I've had much to do with LilyPond, but it seems that the installer is STILL fiddling with the registry in terms of python. What I would like to see: 1. Could the "call registry_python" line in the lilypond.nsh (or whatever) file used for generating the installer be disabled or made optional. 2. If number 1 isn't an option, could an installer 'without' this step be put out? 3. If number 1 isn't an option, at least provide just a zipped archive of all the files that are supposed to be installed by the installer so that I don't have to reset my python install every time I do this. LilyPond's bundled python is useless (unless something has changed in the past 6 months), so I don't see why it is still bundled. Regards, J. Leung _ Need more speed? Get Xtra Broadband @ http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
Hi, On Wed, 21 Feb 2007, J L wrote: > LilyPond's bundled python is useless (unless something has changed in > the past 6 months), so I don't see why it is still bundled. Maybe it is bundled, because LilyPond _needs_ Python? And Windows users are typically too clueless to install all needed dependencies, so you have to do it for them? Hth, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
J L escreveu: > Hi, > > It's been a while since I've had much to do with LilyPond, but it seems > that the installer is STILL fiddling with the registry in terms of python. > > What I would like to see: > 1. Could the "call registry_python" line in the lilypond.nsh (or > whatever) file used for generating the installer be disabled or made > optional. patches thoughtfully considered. > -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Windows Releases
LilyPond's bundled python is useless (unless something has changed in the past 6 months), so I don't see why it is still bundled. It is needed an perfectly good to run convert-ly. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
