On 29/12/24 10:35, Raghav Gururajan wrote:
Guix Committers!
There's org created for Guix on Codeberg to setup mirrors for Guix's
repositories. Please let me know if you'd like to become owner of the
namespace and I'll add you.
Reference: https://codeberg.org/Codeberg-e.V./requests/issues/498
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?
T
On 2025-01-03 6:24 PM, Ian Eure wrote:
Hello Guixers,
I’ve applied for, and received, my commit bit! The manual says to send a
signed email to say so, so that’s what I’m doing.
By way of introductions: I’ve been using Linux since around 1995, when I
installed Slackware off floppy disks I mad
On Wed, Jan 01, 2025 at 05:13:28AM -0500, 45mg wrote:
> The only approach I'm aware of is to just ignore such tests. Examples of
> this I've seen:
It's fine to ignore these tests. We don't need to run every single
upstream test if it's too inconvenient.
Hi all! I just want to mention some theoretical benefits that could arise from
using a Guix-aware build-system.
A Guix-aware build system could improve upon the traditional timestamp-based
rebuilding heuristic by using a content address heursitic. This benefits
developers using the Guix-aware b
Hey Hilton, thanks for the feedback.
These were the general paths I was looking at.
A . Manually
Guix shell with zig
Build regular Ghostty. Here, I'd follow the official direction on Building
Ghostty from Source.
https://ghostty.org/docs/install/build
Build Ghostty with guix + custom build step
