From: HiPhish <hiphish@posteo.de>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Mon, 25 Feb 2019 00:00:55 +0100 [thread overview]
Message-ID: <14132372.7nNnX97SN8@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <871s40jdk4.fsf@ambrevar.xyz>
On Friday, 22 February 2019 11:57:31 CET you wrote:
> I can merge this in your name, let me know.
That's fine by me. You are right about the missing install phase, I was
primarily trying to get it to build first before worrying about installing the
files.
How do you know how to do these things? I read the manual and I couldn't find
the programming interface to changing phases. Do you read the source code of
Guix to come up with these things?
As for the .desktop file and icon, I'd just leave those two open for now. From
the looks of it, the eDuke32 project has none, so they should be added to the
eDuke32 project itself, then we can add those parts to the install phase
later.
next prev parent reply other threads:[~2019-02-24 23:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 8:20 Need help porting eDuke32 HiPhish
2019-02-17 15:33 ` Pierre Neidhardt
2019-02-17 16:21 ` HiPhish
2019-02-21 19:19 ` Pierre Neidhardt
2019-02-21 19:22 ` Pierre Neidhardt
2019-02-21 19:27 ` Pierre Neidhardt
2019-02-21 20:27 ` HiPhish
2019-02-22 10:36 ` Pierre Neidhardt
2019-02-22 10:57 ` Pierre Neidhardt
2019-02-22 13:01 ` Pierre Neidhardt
2019-02-24 23:04 ` HiPhish
2019-02-25 16:09 ` Pierre Neidhardt
2019-02-25 17:51 ` Andreas Enge
2019-02-25 18:59 ` Giovanni Biscuolo
2019-02-26 9:57 ` Tobias Geerinckx-Rice
2019-02-26 10:00 ` Pierre Neidhardt
2019-02-26 11:18 ` HiPhish
2019-02-26 14:25 ` Ricardo Wurmus
2019-02-26 15:41 ` Jack Hill
2019-02-26 20:50 ` swedebugia
2019-02-24 23:00 ` HiPhish [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-16 9:49 HiPhish
2019-02-16 10:30 ` Pierre Neidhardt
2019-02-16 12:15 ` nee
2019-02-16 12:20 ` Pierre Neidhardt
2019-02-16 16:45 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14132372.7nNnX97SN8@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).