From 2ed20ae542b8fb12a313cdebbd1be42447d4277c Mon Sep 17 00:00:00 2001 From: Valentin Villenave Date: Thu, 27 May 2010 18:45:12 +0200 Subject: [PATCH] Doc: update CG "Working with source code" The possibility to download the source code as a tarball wasn't mentioned at all; I added it for completeness' sake, whilst explicitely discouraging it in favor of git stuff. --- Documentation/contributor/source-code.itexi | 26 ++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi index 80e4358bd2..aae0a93cf3 100644 --- a/Documentation/contributor/source-code.itexi +++ b/Documentation/contributor/source-code.itexi @@ -6,6 +6,7 @@ @menu +* Downloading the source code as an archive:: * Using lily-git:: * Starting with Git:: * Basic Git procedures:: @@ -16,6 +17,29 @@ @end menu +@node Downloading the source code as an archive +@section Downloading the source code as an archive + + +An easy way to get the complete source code is to download it +as a @qq{tarball} archive, that can be extracted on any operating +system (Windows users may have to download and install the free-software +@uref{http://www.7-zip.org, 7zip archiver} to extract it. + +Such a tarball is directly available on the LilyPond website: see +@rweb{Source}. This source code matches the proposed binaries on +the same page (i.e. the latest stable or development release). + +Another way to retrieve the latest LilyPond snapshot from its +GNU Savannah Git server is to click on the following link: +@uref{http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=snapshot}. + +However, please note that this will not allow you to submit your +modifications to the code in a proper way. Therefore the recommended +way of getting the source code (alongside with its complete history log) +is by using Git, as explained in this section. + + @node Using lily-git @section Using lily-git @@ -863,7 +887,7 @@ that looks like this: # Changes to be committed: # (use "git reset HEAD ..." to unstage) # -# modified: working.itexi +# modified: working.itexi # @end example -- 2.39.2