[Top][All Lists]

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

[Gnash-commit] [SCM] Gnash branch, release_0_8_8, updated. 27c0cb14b79ad

From: Rob Savoye
Subject: [Gnash-commit] [SCM] Gnash branch, release_0_8_8, updated. 27c0cb14b79adb4ef9afc806d51c459de962dc36
Date: Sat, 21 Aug 2010 14:25:23 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gnash".

The branch, release_0_8_8 has been updated
       via  27c0cb14b79adb4ef9afc806d51c459de962dc36 (commit)
      from  643125560ceb01b9d484e18c4b559b60c7bd25a2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------

commit 27c0cb14b79adb4ef9afc806d51c459de962dc36
Author: Rob Savoye <address@hidden>
Date:   Sat Aug 21 08:25:14 2010 -0600

    rename from README_bzr, change bzr to git

diff --git a/README.git b/README.git
new file mode 100644
index 0000000..e20fd35
--- /dev/null
+++ b/README.git
@@ -0,0 +1,57 @@
+               Building Gnash from its git repository
+The source code of Gnash is checked into a git repository.  (See the main
+web page for Gnash for the current details on where that repository is.)
+The instructions for building Gnash in README and INSTALL assume that
+you are starting from a released "tarball" (e.g. gnash-VERSION.tar.gz).
+The tarball contains some files that are not in the original source code
+in git.  They are generated using tools that not everyone is expected
+to have.  This simplifies the process of building Gnash releases, for
+ordinary people.
+People who are actively working on maintaining Gnash need to have these
+extra tools.  They are used to build configuration files, international
+message translation catalogs, and such.  After you check out the source
+code of Gnash from git, you'll have to run a single script that rebuilds
+all these files.  This script is called "./", and it lives
+in the top-level directory of gnash.  You run it without any arguments.
+When it finishes, you can run "./configure", with or without arguments,
+as instructed in the README and INSTALL files.
+A variety of GNU programs are required when checking out the
+git tree and building the auto-generated files.  If anything is
+missing, ./ will (probably) tell you, or produce a relatively
+understandable error message.  When in doubt, look at the *first*
+error message.  Here are the programs required:
+GNU            Minimum         RPM or DEB package names:
+Package                Version  Debian         Ubuntu          Fedora          
+-------         -------  -----------    ------------    ---------      
+automake       1.9.6   automake1.9     automake1.9     automake
+autoconf       2.59                    autoconf        autoconf
+git            1.3                     git             git
+gettext                0.14.6                  gettext         gettext
+libtool                1.5.22                  libtool         libtool
+               1.5.22                  libltdl3-dev    libtool
+The "Minimum Version" is not necessarily the lowest version that will work;
+it's the lowest version that the Gnash team has recently tested with.  
+(You'll also need some very common tools, for example the standard Unix/GNU
+core utilities (ls, mv); text utilities (grep, sed), and shell (sh).
+Unless your system is very unusual, these will already be installed.)
+The version dependencies among these tools are, unfortunately, more
+complicated than we can describe here.  When ./ is failing
+for you, either upgrade all the things in the above table to the latest
+version available (which may break other packages you're trying to build),
+or seek a compatible set of tools, perhaps the set that comes by default
+in your operating system (if any).
+If you are unable to run ./ successfully on your system, consider
+building Gnash from a tarball release.  Or, move the git tree to a system
+on which you can run ./ successfully, then move it back to the
+system you are trying to build on.
+Once ./ completes successfully, you can go on with the normal
+instructions found in the README file.


Summary of changes:
 README_bzr => README.git |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)
 copy README_bzr => README.git (86%)


reply via email to

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