Doom engines
Hans de Goede
hdegoede at redhat.com
Sun Aug 21 02:59:44 UTC 2011
Hi,
On 08/20/2011 04:17 AM, Rahul Sundaram wrote:
> Hi
>
> Vavoom has already been packaged for a long time in Fedora and uses
> autodownloader for enabling users to use the shareware data easily. I
> have recently packaged a alternative Doom engine called Chocolate Doom
> [2] which is a more conservative port that aims to be more compatible
> with mods. I could package other Doom engines out there including
> odamex[2], some of them unique. It doesn't make much sense to
> duplicate the autodownloader related files. Debian has some guidelines
> [3] What would be the best way to handle this?
>
> References:
>
> 1. https://bugzilla.redhat.com/show_bug.cgi?id=730851
> 2. http://odamex.net/
> 3. http://pkg-games.alioth.debian.org/doom-packaging/
First of all thanks for doing the vavoom update!
Now about this thread (which I've read entirely but I was not sure
where to jump in).
I think it would make sense to have a single common package
for autodownload files, .desktop files and .sh files, we need
to figure out what to do with the .sh files when multiple engines
are installed (pick a default, add a switch to allow overriding
it from the cmdline I guess). I suggest calling it
"doom-autodownload-helpers".
As for the interaction with doom-shareware from rpmfusion, we
could make it first check if that is installed, and if so
not check for the files under ~ and use autodownload to get
them at all, instead simply launching $engine with the necessary
options to use the files under /usr/share put there by the
rpmfusion package.
Regards,
Hans
More information about the games
mailing list