From: Hilton Chain <hako@ultrarare.space>
To: Timothy Washington <twashing@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bootstrapped Zig now available in Guix master.
Date: Fri, 03 Jan 2025 22:20:30 +0800 [thread overview]
Message-ID: <87r05km11t.wl-hako@ultrarare.space> (raw)
In-Reply-To: <CAADtM-ao38pu-E=n86vQTN8O2O6EBOVp93mqzCoB6rvjAANhoA@mail.gmail.com>
Hi Timothy,
On Thu, 02 Jan 2025 09:09:10 +0800,
Timothy Washington wrote:
>
> Hi there Hilton,
>
> This is a great achievement and I appreciate your work on this. I have my
> eye on packaging Ghostty for geeks when I came across your work here. Are
> you also eyeing packaging Ghostty as well? If not, then don't mind me. If
> so, is there anything a Zig and Guix noob can help with?
I have checked it briefly but I'm not going to package it. There's one package
in an external channel[1], you can try it there for now. Note its definition is
currently written in a way that cannot be accepted into Guix.
Examples for Zig packages are available in (gnu packages zig-xyz) module[2], I
think zig-build-system can support Ghostty well, but the package itself is a bit
complex, so I would advise against packaging it if you don't have much
experience.
Thanks
---
[1]: https://toys.whereis.social/?search=ghostty
[2]: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/zig-xyz.scm
next prev parent reply other threads:[~2025-01-03 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 1:09 Bootstrapped Zig now available in Guix master Timothy Washington
2025-01-03 14:20 ` Hilton Chain [this message]
2025-01-05 3:44 ` Timothy Washington
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 14:39 Bootstrapping Zig with no binary blobs: status update and call for packages Hilton Chain
2024-12-31 15:39 ` Bootstrapped Zig now available in Guix master Hilton Chain
2024-12-31 15:57 ` Ekaitz Zarraga
2025-01-01 5:25 ` Pjotr Prins
2025-01-03 14:38 ` Hilton Chain
2025-01-03 18:01 ` Attila Lendvai
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=87r05km11t.wl-hako@ultrarare.space \
--to=hako@ultrarare.space \
--cc=guix-devel@gnu.org \
--cc=twashing@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).