anne/lyx_mirror
1
0
Fork 0
mirror of https://git.lyx.org/repos/lyx.git synced 2024-11-05 13:26:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update our documentation to mention git instead of svn.

Browse Source 
Note that some mentions of svn remain in
* development/cmake/LyxPackaging.cmake
* development/LyX-Mac-binary-release.sh
* development/Win32/packaging/installer/settings.nsh
This commit is contained in:
Jean-Marc Lasgouttes 2013-05-27 18:13:09 +02:00
parent 7e188c515e
commit aaacbe579b
3 changed files with 10 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
INSTALL.MacOSX
View File

@ -93,7 +93,7 @@ The aspell library is GPL-licensed and can be downloaded from
ftp://ftp.gnu.org/gnu/aspell or one of the mirrors.
At the time of writing aspell-0.60.tar.gz is the current version.
Unpack the tarball in the same directory where you placed the
svn checkout or LyX tarball.
git checkout or LyX tarball.
BUILD INSTRUCTIONS
@ -210,7 +210,7 @@ adjust some environment variables to do so.
user's directory being located at ~/Library/Application Support/LyX-2.0)
(b) Developmental Versions (svn checkouts)
(b) Developmental Versions (git checkouts)
Building LyX from developmental sources requires a few more steps.
Instead of the instructions above, do the following:
@ -228,10 +228,6 @@ Instead of the instructions above, do the following:
make
make install-strip
Note that by default svn versions use some extra debugging code that
somewhat slows LyX down. If it is a real problem, you can pass the
option --enable-build-type=release to configure.
(c) Distribution build
@ -254,7 +250,7 @@ Per default the resulting LyX application is build for ppc and i386
to be usable on all systems from Tiger upwards.
(d) Developmental Versions (svn checkouts and Qt4 frameworks)
(d) Development Versions (git checkouts and Qt4 frameworks)
Instead of the instructions in (b), do the following:

12
README
View File

@ -70,13 +70,13 @@ How does the LyX version scheme work?
shows that these releases will contain a few new features, and
that the bulk of the patches will be documentation updates.
If you get the source from Subversion, the version string will
look like one of:
If you get the source from Git, the version string will look like
one of:
1.5.1svn -- this is the stable branch on which maintenance
release 1.5.1 will eventually be tagged.
1.6.0svn -- this is the main branch on which stable
release 1.6.0 will eventually be tagged.
2.0.6dev -- this is the stable branch on which maintenance
release 2.0.6 will eventually be tagged.
2.1.0dev -- this is the main branch on which stable
release 2.1.0 will eventually be tagged.
What's new?

2
config/lyxinclude.m4
View File

@ -22,7 +22,7 @@ AC_ARG_ENABLE(build-type,
*) AC_MSG_ERROR([bad build type specification \"$enableval\". Please use one of rel(ease), pre(release), dev(elopment), prof(iling), or gprof]);;
esac],
[case AC_PACKAGE_VERSION in
*svn*|*dev*) build_type=development;;
*dev*) build_type=development;;
*pre*|*alpha*|*beta*|*rc*) build_type=prerelease;;
*) build_type=release ;;
esac])