[debbugs-tracker] bug#35720: closed ([PATCH] gnu: Add chocolate-doom.)

[GNU bug Tracking System]

Your message dated Fri, 24 May 2019 10:54:13 -0400
with message-id <address@hidden>
and subject line Re: [bug#35720] [PATCH] gnu: Add chocolate-doom.
has caused the debbugs.gnu.org bug report #35720,
regarding [PATCH] gnu: Add chocolate-doom.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
35720: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35720
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] gnu: Add chocolate-doom. Date: Mon, 13 May 2019 15:42:52 -0400 User-agent: Mutt/1.10.1 (2018-07-13)

Patch adding a package for Chocolate Doom, which I felt was appropriate
as both Odamex and GZDoom are packaged in Guix.

Regards,
Jakob L. Kreuze

0001-gnu-Add-chocolate-doom.patch
Description: Text Data

signature.asc
Description: Digital signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [bug#35720] [PATCH] gnu: Add chocolate-doom.
>
>
>
>
> Date: 
>
> Fri, 24 May 2019 10:54:13 -0400
>
>
>
>
> User-agent: 
>
> mu4e 1.2.0; emacs 26.2
>
>
>
>
> Jakob L. Kreuze writes:
>
> > GZDoom adds a reference to /share/games/doom because it bundles a .pk3
> > file containing some port-specific things which ends up in the store,
> > and my understanding is that Freedoom updates DOOMWADDIR and DOOMWADPATH
> > to point to where the wads are in the profile, so I don't think patching
> > the search paths is necessary.
> >
> > Thanks for reviewing this!
> >
> > Jakob
>
> At any rate, I discovered that the freedoom script actually *itself*
> searches for a possible binary and launches it with the appropriate WAD
> given as an argument, of which chocolate-doom is considered a valid
> option.
>
> So, seems good!  I pushed the patch to Guix master... chocolate-doom is
> now part of Guix :)
>
> Congrats on getting in your first package!  Great work, Jakob.
>  - Chris
>
>
> --- End Message ---