by Rahul Sundaram
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
 which is a more conservative port that aims to be more compatible
with mods. I could package other Doom engines out there including
odamex, some of them unique. It doesn't make much sense to
duplicate the autodownloader related files. Debian has some guidelines
 What would be the best way to handle this?
11 years, 8 months
Fwd: Re: freedoom 0.8 release?
by Rahul Sundaram
If anyone has thoughts on how to proceed, let me know
-------- Original Message --------
Subject: Re: freedoom 0.8 release?
Date: Sun, 21 Aug 2011 00:30:30 -0700
From: Mike Swanson
To: Rahul Sundaram
CC: Simon Howard, RjY , catoptromancy
On Sat, Aug 20, 2011 at 2:03 PM, Rahul Sundaram wrote:
> I was thinking of pulling in the latest git snapshot for Fedora and
> built it today. I have the following wad files
> Currently in Fedora, we have two different packages, freedoom and
> freedoom-dm and I am wondering how I should proceed? What's the diff
> between doom.wad and doom2.wad I could have the latest freedoom
> obsolete freedoom-dm and move forward. Let me know what the
> recommended way of packaging these is.
The first three files are IWADs; files that contain the complete data
for a Doom engine to run. Effectively you can ignore the
freedoom*.wad files for packaging, as they all only contain patch data
doom.wad contains resources to support "The Ultimate Doom", the retail
version of Doom 1. doom2.wad contains the resources to support Doom
II and Final Doom, which the majority of PWADs (new levels, for
example) require. freedm.wad is the death-match only IWAD, it
contains the same resources as doom2.wad except for a different level
Personally I don't have a recommended way of packaging, although
Debian (sorry, I'm a Debian user :P) seems to rename our doom2.wad to
"freedoom.wad" (unrelated to the PWAD built from the source tree),
presumably to avoid a conflict with id Software's Doom II. For
compatibility purposes, our IWADs are named the same as the commercial
games, but wanting both Doom and Freedoom installed system-wide would
result in conflicting file names.
11 years, 9 months
orphaning / looking for new owner for monkey-bubble
by Hans de Goede
I've been thinking about orphaning monkey-bubble for a while now,
mostly because it is dead upstream and it is using various obsolete
gnome technologies (esound, libgnomeui, bonobo).
Yesterday it came to my attention that monkey-bubble also contains
at least 1 sound sample which we should not be re-distributing, as
well as various sound samples from unclear origin. This has helped
me make up my mind, and unless someone else jumps in to take it over
(and fix the sound sample situation) I'm going to orphan it.
So anyone want to take over monkey-bubble?
11 years, 10 months