Work correctly when ~/.config directory does not exist.
Use the default skin instead of plain skin by default to work
around font issues in plain skin.
freedb issue pointed out by naddy@
Other issues pointed out by nick@
Two patches seem to have no effect: the first one fixes a C++ issue I
do not see on amd64 when building without it, the second one supposedly
fixes translation files, but without it I can switch between languages
just fine.
Both patches are there since import on 2014 and I they probably used to
be relevant for older Mumble versions, but not so much today anymore.
This "remove broken files" patch disables theme files such as
"Mumble/OSX Dark.qss" which break the build with BSD make(1), which chokes
on whitespaces in file names (even when escaped with backslashes).
GNU make can cope with escaped whitespaces, everything builds fine with
gmake(1). Since we are not OS X, these theme files are not installed
anyway, so no PLIST change.
Remove the patch and set USE_GMAKE; reason for this is that Mumble no
longer errors out silently at runtime due to the patched file and disables
the "Dark" style as a consequence (seen in developer console):
<W> ... Style "Dark" of theme "Mumble" references invalid qss \
":themes/Mumble/OSX Dark.qss" for platform "MAC" , skipping theme
<W> ... Could not find configured theme "Mumble"
<W> ... Applying fallback style sheet
With this commit, Mumble shows no warnings and allows me to use the "Dark"
style:
<W> ... Theme: "Mumble"
<W> ... Style: "Dark"
<W> ... --> qss: ":themes/Mumble/Dark.qss"
Doing so is correct, but the patched code is under "linux* { ... }" in the
qmake file and therefore does not effect our build at all.
The resulting Makefile did not change after removing this patch, everything
built and linked fine as exepcted.
clang defines __ppc__, unlike ports-gcc that was used previously, and
tries to make use of obsoleted Darwin (Mac OS X) flavored assembly code.
Use the C code instead, until upstream decides what to do about this.
Thanks a lot to gkoehler@ for further precisions!
While here, move HOMEPAGE to https.
OK bcallah@
Just use /var/spool/mpd as the home dir but tweak the perms to prevent
group write access and avoid security(8) warnings. If you already have
mpd installed you might want to update the home dir by hand as
documented in the README.
Prompted by questions and diffs from chrisz@ and a report from Moises
Simon, input from ratchov@ and sthen@, ok sthen@