prboom-users

[Prboom-users] PrBoom

[Serge J. <azr...@gm...>]

Greetings.

We from Vulture Software are developing a mod for Doom II.
It is nearly completed and it was originally intended for Boom (or a Boom
supporting port).

After a bit of searching, we came to the conclusion that PrBoom is the ideal
engine for our mod in development.

Now, we'd like to include PrBoom in our distribution package ( UNMODIFIED
ofcourse, with all the files included).
We plan to make a professional install program that will install PrBoom on
the user's hard drive with our mod included.

The only thing the user would have to do is copy the Doom2 IWAD to the
PrBoom directory and with a simple Batch program he would be able to load
our mod directly using the PrBoom engine.

I'd like to know if we have your permission to do that.

Thanks.
Vulture Software (www.teamhellspawn.com/vulturesoftware)

Re: [Prboom-users] PrBoom

[nicolas <nic...@on...>]

Le 11.09.2006 12:36:57, Serge Jaeken a =E9crit=A0:

> We from Vulture Software are developing a mod for Doom II.
> It is nearly completed and it was originally intended for Boom (or a =20
> Boom supporting port).

> After a bit of searching, we came to the conclusion that PrBoom is =20
> the ideal engine for our mod in development.

[...]

> I'd like to know if we have your permission to do that.

As long as prboom is protected by the GNU/GPL, you don't need a =20
permission here, but you should read the GNU/GPL first.
You should instead develop a WAD file, so that any prboom user would be =20
able to copy the right file in the right place, especially Linux or BSD =20
users.
Read more on the doom wiki. http://doom.wikia.com/
And go in a Doom website (Doomworld, Newdoom and friends).

nicolas patrois : pts noir asocial
--=20
PIGEONS

P : Avoue quand m=EAme qu'il n'y a rien de plus idiot que de ramasser des =20
crottes =E0 moto !
M : Il n'y a pas de sots m=E9tiers !
P : Non... il n'y a que des cons pour les faire !

Re: [Prboom-users] PrBoom

[Colin P. <cp...@mo...>]

Serge Jaeken wrote:
> We from Vulture Software are developing a mod for Doom II.
> It is nearly completed and it was originally intended for Boom
>  
> After a bit of searching, we came to the conclusion that PrBoom is the
> ideal engine for our mod in development.
>
> Now, we'd like to include PrBoom in our distribution package (
> UNMODIFIED ofcourse, with all the files included).

You should note that if you distribute PrBoom then you must either
include the source code, or offer to provide source code on request, on
terms as described in section 3 of the license.

You don't have to distribute it unmodified. The license specifically
allows you to make & distribute modified versions, provided you offer
the source code for the modified work under the same license. And you
can leave out files that you don't need (much of the Boom & MBF docs,
for instance, are really for developers); only the license and copyright
files (COPYING and AUTHORS) must be included.

> We plan to make a professional install program that will install PrBoom
> on the user's hard drive with our mod included.
>  
> The only thing the user would have to do is copy the Doom2 IWAD to the
> PrBoom directory and with a simple Batch program he would be able to
> load our mod directly using the PrBoom engine.
>  
> I'd like to know if we have your permission to do that.

I am one of the authors of PrBoom. Certainly you are welcome to use
PrBoom - we are, in effect, the current version of Boom, so it is a
sensible choice - in accordance with the license terms.

I have assumed that your request is out of politeness, and you are not
asking for any formal legal permission. PrBoom is open-source, so you
don't need any extra permission from us to distribute it, or to
aggregate it with your own work, provided you are able to work within
the existing license terms. WAD files are 'independent and separate
works' in the terms of section 2 of the license (see the file
'copying'), so you can distribute your WAD file on your own terms and
distribute PrBoom alongside it. I imagine that the install program would
be interpreted as a separate work in the same way.