Bug#679033: 0ad doesn't start when /usr/games is not in PATH

[Vincent Cheng]

tag 679033 + confirmed
thanks

On Mon, Jun 25, 2012 at 2:13 PM, Ansgar Burchardt <ansgar at debian.org> wrote:
> Package: 0ad
> Version: 0~r11863-2
> Severity: normal
>
> 0ad doesn't start when /usr/games is not in PATH:
>
> $ /usr/games/0ad
> Error: pyrogenesis cannot be found in /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
<snip>

As far as I'm aware, /usr/games is in PATH by default (aside from
root), so end users who don't tinker with their PATH should be able to
start 0ad without a problem.

However, I admit that the cause of this bug is one of my
Debian-specific patches. Upstream simply hardcodes the path to 0ad's
pyrogenesis engine (see source at [1]), which I believe is an
inflexible and inappropriate solution (and I had to patch the file
anyways since the Debian 0ad package installs pyrogenesis into
/usr/games, as per Debian Policy).

There's an ongoing discussion about this issue in upstream's bug
tracker [2]. If there's anything that's relevant that neither I nor
upstream has considered yet, please feel free to point it out. :)

Regards,
Vincent

[1] http://trac.wildfiregames.com/browser/ps/trunk/build/resources/0ad.sh
[2] http://trac.wildfiregames.com/ticket/1424