From: "Murilo" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "boogs" <boogs@venatores.group>, <75237@debbugs.gnu.org>
Subject: bug#75237: Packaging ghostty terminal
Date: Wed, 01 Jan 2025 10:44:24 -0300 [thread overview]
Message-ID: <D6QS5AANIVYZ.3E3F2IKG2OJ1B@disroot.org> (raw)
In-Reply-To: <8734i3nsea.fsf@venatores.group>
Hi, sadly its not an easy task as you might be expecting it to be.
It vendors a lot of dependencies in the repository and recursive dependency
replacing with zig fetch isn't quite there yet so we have to do some more work,
create a cache and vendor it with --system. I don't know if this is the best
approach since I never touched anything zig, but it seems to be the easiest from
my research.
Fortunately I've already went through the trouble and packaged it on my channel
a couple days ago so you can use it right away :)
Feel free to take a look at my package definition [0] or use my channel [1]. I
plan to upstream it here once holidays are over and I have some free time, whats
left to do is looking at the vendored sources one by one to ensure everything is
free and there are no nasty pre-built stuff inside the sources, and see if any
of it can be made into a proper guix package so we can use it as normal inputs.
Feel free to help with those too if you want to, the more help the merrier :)
[0] https://codeberg.org/look/saayix/src/branch/entropy/saayix/packages/terminals.scm
[1] https://codeberg.org/look/saayix
next prev parent reply other threads:[~2025-01-01 14:23 UTC|newest]
Thread overview: 3+ 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 [this message]
2025-01-01 18:12 ` boogs via Bug reports for GNU Guix
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=D6QS5AANIVYZ.3E3F2IKG2OJ1B@disroot.org \
--to=bug-guix@gnu.org \
--cc=75237@debbugs.gnu.org \
--cc=boogs@venatores.group \
--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 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).