GitHub archives now extract to omarchy-mlx-<ver> for every tag, so the
source filename and the build cd follow the omarchy-mlx name. Tarball
sha256 unchanged: 7ad98f7df4df54c1e194b2be1469200da767dc3e374d79e66dcb98bdbb958a9d.
omarchy-mlx builds the v0.7.10 release wheel and vendor tarball from
github.com/joshuaswarren/omarchy-mlx; omarchy-mlx-vulkan pins the
honeykrisp-omarchy-v3 driver at mesa-1 e7631595df6281748ea5e643d74db59c5f783b01
with MESA_GIT_SHA1_OVERRIDE set to the short sha the driver reports and the
runtime compares. omarchy-mac-ml now pulls omarchy-mlx-vulkan directly and its
description names MLX on the GPU and Core ML models on the Neural Engine.
Both packages come from one PKGBUILD, so the MLX wheel and the Vulkan
driver it was qualified on publish together.
omarchy-mlx-vulkan builds only the Honeykrisp Vulkan driver from
joshuaswarren/mesa-1 9b97b82ab1. It installs the driver, an ICD
manifest with an absolute library_path, and the driver's git SHA in
/usr/lib/omarchy-mlx/vulkan/. The manifest is outside the loader's
search path, so only omarchy-mlx uses the driver. It provides nothing
generic and conflicts with mesa-honeykrisp-omarchy.
omarchy-mlx builds the private venv offline from the release's
hash-locked vendor wheels and depends on the exact omarchy-mlx-vulkan
build.
The mlx-omarchy sources are placeholders until v0.7.7 is published.
Joshua Warren