Package Details: ghostty-git 1.0.1.r399.ga244535-1

Git Clone URL: https://aur.archlinux.org/ghostty-git.git (read-only, click to copy)
Package Base: ghostty-git
Description: Fast, native, feature-rich terminal emulator pushing modern features
Upstream URL: https://github.com/ghostty-org/ghostty
Licenses: MIT
Conflicts: ghostty
Provides: ghostty
Submitter: gpanders
Maintainer: gpanders (alerque)
Last Packager: gpanders
Votes: 9
Popularity: 3.65
First Submitted: 2024-06-07 14:51 (UTC)
Last Updated: 2025-01-13 02:05 (UTC)

Required by (1)

Sources (1)

Latest Comments

1 2 3 Next › Last »

alerque commented on 2025-01-16 12:58 (UTC)

@adrinux Upstream seems to be miss-handling resources based on what is or isn't available user home directories; that has nothing to do with this packaging.

adrinux commented on 2025-01-15 10:17 (UTC)

The missing resources (including themes) is an ongoing upstream issue https://github.com/ghostty-org/ghostty/discussions/3500

Ghostty reported it was looking in $HOME/.config/ghostty for the themes. Since they're all in /usr/share/themes I just added a symlink as a workaround.

cd ~/.config/ghostty
ln -s /usr/share/ghostty/themes themes

My version is 1.0.1-r428

alerque commented on 2025-01-13 22:32 (UTC) (edited on 2025-01-13 22:43 (UTC) by alerque)

@yamafaktory As of yesterday when I was working on overhauling this, the file list in the final package does include the themes. If it doesn't now that's likely an upstream bug in Git HEAD, not in this packaging, we're currently coping everything in the build directory, then selectively removing a couple bits that we're putting in split packages. We're not removing themes.

Possibly upstream changed where they look for resources vs. where they build them to. But it isn't necessarily incumbent on this packaging to fix upstream bugs.

Edit: I just rebuilt the package now and far from not having themes, it has 16 more themes than yesterday when I built it. How exactly are you building the packages? And what exact version do you get? It is possible there was a problem upstream post 1.0.1.r379 (yesterday) and pre 1.0.1.r418 (now).

yamafaktory commented on 2025-01-13 09:29 (UTC)

The themes are completely missing for me at the moments (ghostty +list-themes complaining about Could not find the Ghostty resources directory.). The workaround is to manually download https://github.com/ghostty-org/ghostty/blob/main/build.zig.zon#L82, extract the archive, move the ghostty directory with all the themes to the right place and rename it to themes.

alerque commented on 2025-01-11 20:40 (UTC)

Thanks for the add @gpanders. I've given this a "light" once over ;-) It's now split up into subpackages equivalent to the stable packaging (including relevant provides and conflicts), versioned with a semantic version relative to the stable versioning, properly linked to library sonames, and styled like the stable PKGBUILD so that diffing it should show pretty minimal differences and act as a bell-weather for what needs to happen when bumping the stable version. For example right now the wayland build option and extra dependencies are pretty clear and having everything worked out ahead of time in the VCS packaging here should make stable bumps fast and correct.

alerque commented on 2025-01-11 12:52 (UTC) (edited on 2025-01-11 19:44 (UTC) by alerque)

@Zane you are free to add v3 optimizations yourself but it should definitely not be packaging defaults. In all likelihood when Arch does get infrastructure spun up for other architectures, v3 will be it's own target architecture entirely. For now x86_64 packages are expected to run on all x86_64 platforms, not just some of them.

nezu commented on 2025-01-07 15:24 (UTC)

yeah, works. Thanks

moiiom commented on 2025-01-07 15:16 (UTC)

@nezu there is a new build dependency wayland-protocols

nezu commented on 2025-01-07 09:51 (UTC)

==> Starting build()... 1220dd654ef941fc76fd96f9ec6adadf83f69b9887a0d3f4ee5ac0a1a3e11be35cf5 12207b7a5b538ffb7fb18f954ae17d2f8490b6e3778a9e30564ad82c58ee8da52361 unable to spawn the following command: ExitCodeFailure pkg-config --variable=pkgdatadir wayland-protocols error: the following build command failed with exit code 1: /app/build/src/ghostty/.zig-cache/o/f059ae1eefb69c6c96c37e49fa11d97e/build /usr/bin/zig /app/build/src/ghostty /app/build/src/ghostty/.zig-cache /home/build/.cache/zig --seed 0x526ba2 -Z54dc142b14c2783c --system -Doptimize=ReleaseFast -Demit-docs ==> ERROR: A failure occurred in build().

gpanders commented on 2025-01-01 16:35 (UTC)

@chauncey The issue doesn't reproduce for all Arch users (including myself) and the discussion in that thread indicates that switching to epoll doesn't work for all users. At this time I think we should leave it to individual users to either patch the PKGBUILD themselves or build Ghostty from source with that patch if it works for them.

1 2 3 Next › Last »