scm is the modern term. vcs is rather used to refer to archaic systems
such as cvs and older. I wish I remembered this before my previous
commit. Oh well...
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22476 57a11ea4-9604-0410-9ed3-97b8803252fd
The code actually has provisions for svn, svk, git and bzr. Only svn and
git are actively used by the core developers though.
This involves changing
- filenames that contained svn while meant for multiple vcs's
- variable and macro names that are relevant for multiple vcs's
- the various locations where the vcs revision info is displayed
to the user, to mention the actual vcs used instead of standard "svn"
While at the last item, I also changed the text printed when gnucash is
called with the --version parameter, to reuse the translatable string
that is also used for the about dialog. This saves us one string to
translate.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22475 57a11ea4-9604-0410-9ed3-97b8803252fd
is read only, the build fails. Fix by only making guile-strings.c if
building from SVN.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19927 57a11ea4-9604-0410-9ed3-97b8803252fd
directory. Also symlink .scm files into the build directory
so it's possible to run from it.
Also fix "fin.scm installed twice", bug #168629.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@13281 57a11ea4-9604-0410-9ed3-97b8803252fd
* intl-scm/xgettext.scm: Add the file name of scheme files to
translation messages.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@7421 57a11ea4-9604-0410-9ed3-97b8803252fd
