lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to update manuals in Frescobaldi?


From: Tom Cloyd
Subject: Re: how to update manuals in Frescobaldi?
Date: Tue, 31 Dec 2013 10:12:11 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 12/31/2013 03:42 AM, Nick Payne wrote:
On 31/12/13 07:51, Federico Bruni wrote:
2013/12/30 Tom Cloyd <address@hidden>
Now that Ly 2.18.0 is out, those of us who use Frescobaldi need to update the manuals it refers to in its Documentation Browser tab.

Nowhere can I find instructions for how to do that. In the Preferences modal window it is possible to indicate a path to "the documentation", but that documentation comes in multiple forms, so I'm at a fork in the road with no map. What does Frescobaldi need?


Frescobaldi needs just a new location for the 2.18  doc.
The quickest way is using the new online url:

You may need updating the documentation browser with Ctrl+R.

If you want to use the offline documentation, type this command (suggested in the download page):


and you'll see an option to download the documentation.

That option doesn't work unless the doc tarball is already downloaded and in the same folder as the install sh. Otherwise it tries to append some of the local path to the doc tarball download link and the download fails:

address@hidden ~ $ sudo sh ~/Downloads/lilypond/lilypond-2.18.0-1.linux-64.sh --doc

lilypond installer for version 2.18.0 release 1,
x86_64 build.
For a list of options, abort (^C) then do:
sh /home/nick/Downloads/lilypond/lilypond-2.18.0-1.linux-64.sh --help


You are about to install LilyPond in /usr/local/lilypond
A script in /usr/local/bin will be created as a shortcut.

Press ^C to abort, or Enter to proceed.

Making /usr/local/lilypond
Creating script /usr/local/bin/lilypond
Creating script /usr/local/bin/lilypond-wrapper.python
Creating script /usr/local/bin/lilypond-wrapper.guile
Creating script /usr/local/bin/uninstall-lilypond
Untarring /home/nick/Downloads/lilypond/lilypond-2.18.0-1.linux-64.sh
No .//home/nick/Downloads/lilypond/lilypond-2.18.0-1.documentation.tar.bz2 found, downloading.
--2013-12-31 21:33:33--  http://lilypond.org/download/binaries/documentation//home/nick/Downloads/lilypond/lilypond-2.18.0-1.documentation.tar.bz2
Resolving lilypond.org (lilypond.org)... 82.94.241.173
Connecting to lilypond.org (lilypond.org)|82.94.241.173|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-12-31 21:33:35 ERROR 404: Not Found.


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user
"That option doesn't work unless the doc tarball is already downloaded and in the same folder as the install sh."

That's sure not what the documentation leads one to believe.

$ sh lilypond-2.18.0-1.linux-x86.sh --help
lilypond-2.18.0-1.linux-x86.sh - install LilyPond tarball
Options
  --batch             no interaction
  --doc               [attempt to] download and install documentation
  --prefix PREFIX     install into PREFIX/lilypond (default: /usr/local)
  --help              this help
  --tarball           extract tar file for archive

I reran it anyway, per your instructions...and one again got the Lilypond 2.16.2 documentation.

Having deleted Lilypond as previously noted - again I ask: where is that documentation coming from? and why isn't the install working as advertised?

t.
-- 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Cloyd, MS MA (LMHC, WA State) 
Cedar City / St. George, UT, U.S.A: (435) 272-3332
* << address@hidden >> (email) << TomCloyd.com >> (website)
* Sleight of Mind blog: Sleightmind.com (mental health issues)
* Trauma Psych blog: http://thetraumapsych.wordpress.com
* Trauma! A PTSD blog: http://www.healthyplace.com/blogs/traumaptsdblog/
* Founder: Google+ Trauma and Dissociation Education and Advocacy community
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

reply via email to

[Prev in Thread] Current Thread [Next in Thread]