Re: Doom engines
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/
Disclaimers, I've not looked at any of this, and I use prboom. :)
My memory of autodownloader is that it checks for the existence of some
file, if it's there, it does nothing and runs the program, and if not, if
downloads it and then runs the program. Could we not do this is such a
way that chocolate uses the same directory stucture for the user-specific
downloaded files as vavoom does? If not, we could at least use vavoom's
structure for the autodownloader portion and symlink from the places
chocolate expects. Then, even if the user uses chocolate first, if they
run vavoom as is currently packaged, it sees what it wants and Bob's your
uncle.
Does this make sense?
-J
Rahul
_______________________________________________
games mailing list
games(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
--
in your fear, seek only peace
in your fear, seek only love
-d. bowie