On Sat, Jun 06, 2009 at 12:11:40AM +0200, Peter Hessler wrote:
Sorry it took so long, but we finally imported this. Many thanks!.
*jump for joy* ;) thanks Peter, i do realize you guys have a lot more
important things to deal with besides games ports, hence i've been
locally keeping all my
Sorry it took so long, but we finally imported this. Many thanks!.
On 2009 Jan 23 (Fri) at 11:42:27 -0800 (-0800), Ryan Freeman wrote:
:hi,
:
:attached is another new tarball of this new port just updating
:to version 1.2.1. regards,
:
:-ryan
--
God isn't dead, He's just trying to avoid the
hi,
attached is another new tarball of this new port just updating
to version 1.2.1. regards,
-ryan
chocolate-doom.tgz
Description: application/tar-gz
Hello ports@
attached is updated tarball with the latest release of chocolate-doom
version 0.2.0. changes can be seen here:
http://chocolate-doom.svn.sourceforge.net/viewvc/chocolate-doom/tags/chocolate-doom-1.2.0/NEWS?view=markup
it may be worthy to note that both chocolate-heretic and
lets also attach port.
On Fri, Dec 12, 2008 at 10:52:37AM -0800, Ryan Freeman wrote:
Hello ports@
attached is updated tarball with the latest release of chocolate-doom
version 0.2.0. changes can be seen here:
On 2008-09-17 02:13:35, Ryan Freeman [EMAIL PROTECTED] wrote:
attached is fixed port again;
- added GPLv2 to Makefile
- removed the trailing whitelines that are getting me in trouble ;)
- SDL under WANTLIB now as per guidance from Antoine
- ${PREFIX}/share/games/doom/ directory is created
On Tue, 16 Sep 2008, Ryan Freeman wrote:
attached is the newest port tarball, tested and working on i386, regards,
Some coments:
- add the GPL version in the license marker
- remove those trailing white lines at the end of DESCR and MESSAGE
- SDL could be in WANTLIB instead of LIB_DEPENDS.
- the
On Wed, Sep 17, 2008 at 09:10:47AM +0200, Antoine Jacoutot wrote:
On Tue, 16 Sep 2008, Ryan Freeman wrote:
attached is the newest port tarball, tested and working on i386, regards,
Some coments:
- add the GPL version in the license marker
- remove those trailing white lines at the end of
hello!
On Tue, Sep 16, 2008 at 12:28:06PM +0200, Paul de Weerd wrote:
Hi Ryan,
Your port doesn't seem to package, apparently because the make fake
step doesn't install the manpages.
thanks for having a look Paul, odd you had that problem. on my laptop,
(of course), it packaged fine, i
On 2008/09/16 03:52, Ryan Freeman wrote:
thanks for having a look Paul, odd you had that problem. on my laptop,
(of course), it packaged fine, i also got a friend who also has i386 and
a newer snapshot than mine that was able to package and repackage.
obtain configure output (or better,
On Tue, Sep 16, 2008 at 12:31:22PM +0100, Stuart Henderson wrote:
On 2008/09/16 03:52, Ryan Freeman wrote:
thanks for having a look Paul, odd you had that problem. on my laptop,
(of course), it packaged fine, i also got a friend who also has i386 and
a newer snapshot than mine that was able
On Tue, Sep 16, 2008 at 06:02:48AM -0700, Ryan Freeman wrote:
| i have fixed this by simply adding a post-install: directive in the port's
| Makefile to copy the manpages which are pregenerated in the tarball anyhow,
| avoiding python once again and now working on my compaq that does not have
|
On Tue, Sep 16, 2008 at 04:34:28PM +0200, Paul de Weerd wrote:
| This one builds, packages and installs fine on amd64. I've made a port
| of the shareware episode 'Knee-Deep in the Dead' (attached) for use
| with this port (and possibly prboom). It'll do until I can locate my
| original Doom
I just keep replying to myself...
On Tue, Sep 16, 2008 at 04:34:28PM +0200, Paul de Weerd wrote:
| I've made a port
| of the shareware episode 'Knee-Deep in the Dead' (attached) for use
| with this port (and possibly prboom). It'll do until I can locate my
| original Doom datafiles.
This
On Tue, Sep 16, 2008 at 04:34:28PM +0200, Paul de Weerd wrote:
| On Tue, Sep 16, 2008 at 06:02:48AM -0700, Ryan Freeman wrote:
| | i have fixed this by simply adding a post-install: directive in the port's
| | Makefile to copy the manpages which are pregenerated in the tarball anyhow,
| | avoiding
*blush* .. Thanks for noticing, Claudio...
Paul 'WEiRD' de Weerd
--
[++-]+++.+++[---].+++[+
+++-].++[-]+.--.[-]
http://www.weirdnet.nl/
doomdata.tgz
Description: application/tar-gz
On Mon, Sep 15, 2008 at 11:59:54PM -0700, Ryan Freeman wrote:
hello ports@
attached is a port of the conservative doom sourceport chocolate-doom.
from DESCR:
Chocolate Doom is a portable branch of the classic doom.exe experience
from the days of DOS. The author, Simon Howard, has worked
Hi,
there's already games/prboom, so why another Doom-engine?
--
Antti Harri
On Dec 13, 2007 10:49 AM, Antti Harri [EMAIL PROTECTED] wrote:
Hi,
there's already games/prboom, so why another Doom-engine?
--
Antti Harri
Because someone ported it?
I don't get this there's already a ported implementation of idea.
Sounds like monopoly.
IMHO, any quality port (as in:
On Thu, 13 Dec 2007, Antti Harri wrote:
I'm not saying it shouldn't be imported, I'm just
wondering what makes chocolate-doom better than
existing prboom.
I would say it tastes better ;-)
--
Antoine
On Thu, 13 Dec 2007, Andrés wrote:
there's already games/prboom, so why another Doom-engine?
Because someone ported it?
I don't get this there's already a ported implementation of idea.
Sounds like monopoly.
IMHO, any quality port (as in: compiles, runs fine) should be included.
With a
On Thu, Dec 13, 2007 at 04:52:20PM +0100, Antoine Jacoutot wrote:
On Thu, 13 Dec 2007, Antti Harri wrote:
I'm not saying it shouldn't be imported, I'm just
wondering what makes chocolate-doom better than
existing prboom.
I would say it tastes better ;-)
hehe well, when it comes to doom and
On Thursday 13 December 2007 05:49:41 Antti Harri wrote:
Hi,
there's already games/prboom, so why another Doom-engine?
Chocolate Doom and PrBoom have very different goals.
PrBoom intends to add many features and remove many limits. Chocolate Doom
intends to behave as much like the original
From the Chocolate Doom README:
Chocolate Doom is a Doom source port which aims to behave as closely
as possible to the original DOS Doom executables.
Chocolate Doom aims to:
* Be compatible with DOS Doom demos
* Be compatible with DOS Doom configuration files
* Be compatible with DOS
Hi Mike,
On Wed, Dec 12, 2007 at 10:48:39PM -0800, Mike Swanson wrote:
From the Chocolate Doom README:
Chocolate Doom is a Doom source port which aims to behave as closely
as possible to the original DOS Doom executables.
Chocolate Doom aims to:
* Be compatible with DOS Doom demos
25 matches
Mail list logo
