From: "Murilo" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: <75237@debbugs.gnu.org>
Subject: bug#75237: Packaging ghostty terminal
Date: Fri, 10 Jan 2025 11:27:19 -0300 [thread overview]
Message-ID: <D6YGP1P9526U.2N1ZMQ6CRAJH@disroot.org> (raw)
In-Reply-To: <8734i3nsea.fsf@venatores.group>
I essentially gave up on packaging ghostty for upstreaming, already spent too
much time on this so I'm moving on.
Will continue to update the current working version on my channel, for personal
use.
Here's my WIP guix branch for ghostty if someone wants to give it a shot, in the
hopes that it might be useful for someone:
https://codeberg.org/look/guix/src/branch/wip-ghostty
https://codeberg.org/look/guix/commits/branch/wip-ghostty
Some zig dependencies there already meet the upstreaming requirements.
The ghostty package does not build, getting some strange errors because of
libvaxis, and missing some zig-mach dependencies.
Might experience some version mismatches because I'm initially using the C
packages we already have packaged on guix.
It needs wuffs which is going to be pain :-(.
The 'fix-path phase substitute* does not work, can be removed, was something I
was experimenting with.
The 'hard-disable-macos-dependencies is also an experiment, might not work.
prev parent reply other threads:[~2025-01-10 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 3:07 bug#75237: Packaging ghostty terminal boogs via Bug reports for GNU Guix
2025-01-01 13:44 ` Murilo via Bug reports for GNU Guix
2025-01-01 18:12 ` boogs via Bug reports for GNU Guix
2025-01-09 23:10 ` Frank J. Cameron
2025-01-10 13:49 ` Murilo via Bug reports for GNU Guix
2025-01-10 15:26 ` Frank J. Cameron
2025-01-10 19:00 ` Frank J. Cameron
2025-01-10 21:21 ` Frank J. Cameron
2025-01-10 14:27 ` Murilo via Bug reports for GNU Guix [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D6YGP1P9526U.2N1ZMQ6CRAJH@disroot.org \
--to=bug-guix@gnu.org \
--cc=75237@debbugs.gnu.org \
--cc=murilo@disroot.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.