FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Games

 
 
LinkBack Thread Tools
 
Old 08-20-2011, 06:27 PM
Rahul Sundaram
 
Default Doom engines

On 08/20/2011 11:49 PM, Jon Ciesla wrote:
> That's not a requirement, just a way to get away with not making a
> separate SRPM. That might be best, actually, maybe doom-shareware-data or
> somesuch?
>
> If you want to make it, I can review it.

That would be a bit of a misleading name since it only has the
autodownloader files and not the data. There was a discussion earlier
in RPM Fusion list about packaging the shareware data there and
potentially dropping the autodownloader files. If we want to continue
to package the autodownloader files separately, the name should be more
specific

Rahul
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-20-2011, 06:28 PM
"Jon Ciesla"
 
Default Doom engines

> On 08/20/2011 11:49 PM, Jon Ciesla wrote:
>> That's not a requirement, just a way to get away with not making a
>> separate SRPM. That might be best, actually, maybe doom-shareware-data
>> or
>> somesuch?
>>
>> If you want to make it, I can review it.
>
> That would be a bit of a misleading name since it only has the
> autodownloader files and not the data. There was a discussion earlier
> in RPM Fusion list about packaging the shareware data there and
> potentially dropping the autodownloader files. If we want to continue
> to package the autodownloader files separately, the name should be more
> specific

I don't think that's a good plan, it would make the engines in Fedora
either unplayable or require RPMFusion, which we can't do.

> Rahul
> _______________________________________________
> games mailing list
> games@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/games
>


--
in your fear, seek only peace
in your fear, seek only love

-d. bowie

_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-20-2011, 06:35 PM
Rahul Sundaram
 
Default Doom engines

On 08/20/2011 11:58 PM, Jon Ciesla wrote:
> I don't think that's a good plan, it would make the engines in Fedora
> either unplayable or require RPMFusion, which we can't do.

Not really. Quake 3 engine (ioquake3) has OpenArena and Doom engines
have Freedoom. So they aren't unplayable

Rahul
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-20-2011, 06:36 PM
"Jon Ciesla"
 
Default Doom engines

> On 08/20/2011 11:58 PM, Jon Ciesla wrote:
>> I don't think that's a good plan, it would make the engines in Fedora
>> either unplayable or require RPMFusion, which we can't do.
>
> Not really. Quake 3 engine (ioquake3) has OpenArena and Doom engines
> have Freedoom. So they aren't unplayable

Oh, I see. Gotcha.

> Rahul
> _______________________________________________
> games mailing list
> games@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/games
>


--
in your fear, seek only peace
in your fear, seek only love

-d. bowie

_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-21-2011, 02:59 AM
Hans de Goede
 
Default Doom engines

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
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-21-2011, 03:06 AM
Rahul Sundaram
 
Default Doom engines

On 08/21/2011 08:29 AM, Hans de Goede wrote:
> First of all thanks for doing the vavoom update!

You are welcome. Do review the changes because I was doing it fairly
blindly. FYI, I have been discussing with freedoom upstream about
doing more regular releases and have updated the current package to the
latest git snapshot locally. I will post the changes for review after
I get some input from upstream.

>
> 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.

I think you are in a better position to do what it is necessary here but
I will be happy to review any new packages. I have already built
Chocolate Doom for Rawhide and Fedora 16 and have been reading up on the
status of the various Doom "ports" for the last few days to figure out
which ones to package. I will post on a update on that too a bit later.

Rahul

Ps: In case anyone is wondering, Doom was one of the games I spend a
lot of time with in a previous life and recent news of the upcoming Doom
3 engine source release motivated me to get involved with Doom again now.
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-21-2011, 01:16 PM
"Jon Ciesla"
 
Default Doom engines

> On 08/21/2011 08:29 AM, Hans de Goede wrote:
>> First of all thanks for doing the vavoom update!
>
> You are welcome. Do review the changes because I was doing it fairly
> blindly. FYI, I have been discussing with freedoom upstream about
> doing more regular releases and have updated the current package to the
> latest git snapshot locally. I will post the changes for review after
> I get some input from upstream.
>
>>
>> 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.
>
> I think you are in a better position to do what it is necessary here but
> I will be happy to review any new packages. I have already built
> Chocolate Doom for Rawhide and Fedora 16 and have been reading up on the
> status of the various Doom "ports" for the last few days to figure out
> which ones to package. I will post on a update on that too a bit later.
>
> Rahul
>
> Ps: In case anyone is wondering, Doom was one of the games I spend a
> lot of time with in a previous life and recent news of the upcoming Doom
> 3 engine source release motivated me to get involved with Doom again now.

Having written a Makefile calling deutex and bsp, I'd say you don't need
an excuse.

> _______________________________________________
> games mailing list
> games@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/games
>


--
in your fear, seek only peace
in your fear, seek only love

-d. bowie

_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-28-2011, 06:37 PM
Hans de Goede
 
Default Doom engines

Hi,

On 08/21/2011 05:06 AM, Rahul Sundaram wrote:
> On 08/21/2011 08:29 AM, Hans de Goede wrote:
>> First of all thanks for doing the vavoom update!
>
> You are welcome. Do review the changes because I was doing it fairly
> blindly. FYI, I have been discussing with freedoom upstream about
> doing more regular releases and have updated the current package to the
> latest git snapshot locally. I will post the changes for review after
> I get some input from upstream.
>
>>
>> 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.
>
> I think you are in a better position to do what it is necessary here but
> I will be happy to review any new packages.

I'm not so sure about me being in a better position, I really don't have
much time if any at all atm to work on this (proof of point, see how
long it has taken me to get around to answering this mail).

So if possible it would be great if you could make the necessary changes,
I will happily help were I can. I think putting the autodl and launch scripts
into a new doom-common package is a good idea.

> I have already built
> Chocolate Doom for Rawhide and Fedora 16 and have been reading up on the
> status of the various Doom "ports" for the last few days to figure out
> which ones to package. I will post on a update on that too a bit later.
>
Regards,

Hans

_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 08-29-2011, 01:43 PM
Rahul Sundaram
 
Default Doom engines

On 08/29/2011 12:07 AM, Hans de Goede wrote:
> So if possible it would be great if you could make the necessary
> changes, I will happily help were I can. I think putting the autodl
> and launch scripts into a new doom-common package is a good idea.

The launch script refers to vavoom by name and I am not sure how to
package that generically so that it could use alternative engines but do
take a look at what I have done

http://sundaram.fedorapeople.org/packages/doom-autodownloader-0.1-1.fc15.src.rpm


Rahul
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 
Old 10-02-2011, 04:13 PM
Hans de Goede
 
Default Doom engines

Hi,

On 08/29/2011 03:43 PM, Rahul Sundaram wrote:
> On 08/29/2011 12:07 AM, Hans de Goede wrote:
>> So if possible it would be great if you could make the necessary
>> changes, I will happily help were I can. I think putting the autodl
>> and launch scripts into a new doom-common package is a good idea.
>
> The launch script refers to vavoom by name and I am not sure how to
> package that generically so that it could use alternative engines but do
> take a look at what I have done
>
> http://sundaram.fedorapeople.org/packages/doom-autodownloader-0.1-1.fc15.src.rpm
>

Sorry for the slow reply. I've taken a quick look, the basis looks good,
some remarks:
1) What provides /usr/bin/doom-engine, is the intend to use alternatives for this?
I think that is a good idea, but we then need to also provide a wrapper script
per engine with standardized cmdline options for specifying for example the datadir where
the wad files are. As the actual options for this may differ per engine. We could try
to see if there is some compatibility between at least chocolate and vavoom and choose
to use a compatible option (if available) in the download + launch script to avoid the
need for a wrapper script.
2) I had the idea that we would also move the heretic shareware, hexen demo and strife-demo
autodl and launch scripts there. They could then use their own /usb/bin/heretic-engine, etc. for this
which would again be provided by alternatives. My reasons fir suggesting also moving these there, are:
a) It is consistent
b) AFAIK other doom engines can play for example heretic too

So how to move forward with this. I'm afraid I've other priorities, so I hope you
can make some time for this. If you can do a new version based on the above comments,
and also a proposed patch for vavoom to move vavoom over to using this, then I'll review
the new package and add the changes to vavoom, does that sound like a good idea?

Note I promise to be quicker with responding the next time around.

Regards,

Hans
_______________________________________________
games mailing list
games@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/games
 

Thread Tools




All times are GMT. The time now is 10:00 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org