mirror of
https://github.com/outbackdingo/hyprcosmic-comp.git
synced 2026-08-25 14:53:22 +00:00
gitops
139a1de4e8
Additive to upstream ci.yml, which is left exactly as it is. That workflow asks whether the code is formatted, lints clean and still compiles under each feature flag, on one Ubuntu runner. None of that stopped being worth asking when the repository was forked, and replacing it would put a conflict in the path of every rebase against pop-os/cosmic-comp for no gain. What it does not ask is whether a distribution has a package called libseat-dev. That question cannot be put to a single Ubuntu runner, so this builds in three containers with three package managers and three sets of names -- a job failing here means a real user of that distribution could not have built it either. Rust comes from rustup because Debian bookworm ships rustc 1.63 and this crate needs 1.93 and edition 2024; the packaged toolchain simply cannot build it on one of the three targets. --default-toolchain none lets rust-toolchain.toml pick the version, so CI cannot drift onto a compiler the project does not use. The last step is the point of the whole thing. `make install` is staged into a DESTDIR and then asserted over: the binary must be at libexec/hyprcosmic, and /usr/bin/cosmic-comp must NOT exist. That is the rule that keeps installing this fork from being a one-way door -- if it will not start, the stock session is still on the greeter's menu to log in and fix it from. Until now that rule lived only in a Makefile comment.