The build now requires gettext v0.19.7 or above.
Removed obsolete files:
* gramps.applications
* gramps.keys
* gramps.mime
Created ITS rules for holidays.xml and tips.xml files.
Included ITS files for shared-mime-info from a gettext v0.20.2
installation.
Attempt to derive the resource path from the package path assuming that
one of the three main installation schemes has been used.
The package path will be one of the following:
<prefix>/lib/pythonX.Y/site-packages
<prefix>\Lib\site-packages
<home>/lib/python
<userbase>/lib/pythonX.Y/site-packages
<userbase>\PythonXY\site-packages
Where <prefix>, <home> and <userbase> are the resource paths used in the
Prefix, Home and User installation schemes.
The use of the command line option "--install-data" in the setup script
is no longer supported.
This change is intended to allow a Gramps core package to be created
as a wheel and installed via pip.
Python 3.6 and above has deprecated illegal string escape sequences. Escape sequences are preceded by a '\' and valid ones are "\n\t\r" etc. Illegal ones are not in the list https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals.
Previous to Python 3.6 these illegal sequences were ignored and the '\' was left in place. Pylint has been noting these for a while now.
This PR corrects these sequences in Gramps. I used
find . -name "*.py" | xargs -t -n 1 python3 -Wd -m py_compile 2>&1 | grep Depre
to locate the failing strings.
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.
