I updated the appdata.xml file to the latest version of the specification
(https://www.freedesktop.org/software/appstream/docs/index.html), adding
some new tags in the process.
I also installed the appdata.xml file to the latest location in the
specification.
The XML has bene validated by the appstreamcli validation tool, and the
patch applied in Debian (Gramps 4.2.3).
If it looks OK, it should probably be cherry-picked to the gramps42
maintenance branch.
I installed my development environment on a different machine
but for some reason didn't install intltool. But it took me
a while to notice since I normally routinely divert the output
to a file. So it was crashing but I didn't know.
But when I examined setup.py I saw that was tested for, at least
it was supposed to be tested for. But on my particular machine
when the test was piped into more commands the whole piped command
was returning a zero status, even though there was no intltool
at all. So I have added an explicit test for intltool and that
does indeed fail on my machine, without one.
With this additional option to setup.py, a path to where the
resource-path will be installed can be supplied. This is needed
when building Gramps out of the source tree, otherwise the temporary
location is stored in the resource-path file and Gramps cannot find
it resources.
* Translation revisions and fixes
* Generate zh_TW.po and new zh_HK.po from zh_CN.po
with the help of https://github.com/BYVoid/OpenCC
and a small sed script (see f.r. 7573 for the script)
So that they're together with the other resources instead of in
site-package/gramps. Aside from a better source and installation
layout, this makes it easier to bundle them.
svn: r22576
Uses GRAMPS_RESOURCES to override the root location of the Gramps data files (which would normally be $(prefix)/share).
In setup.py install, writes $(prefix)/share to gen/utils/resource-path, installs that file, then deletes it again from the source tree. The presence or absence determines whether Gramps is running from the source directory or from an installation.
Const.py is now a static file; const.py.in is no longer used. Note that because importing const into setup tried to initialize things that we don't want initialized, VERSION is removed, and imported from gramps.version -- a file which will be added in the next change. Consequently, this commit will not run.
svn: r21613
