nix-community / nixpkgs-wayland
Automated, pre-built packages for Wayland (sway/wlroots) tools for NixOS. [maintainers=@colemickens, @Artturin]
View on GitHubAI Architecture Analysis
This repository is indexed by RepoMind. By analyzing nix-community/nixpkgs-wayland in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler viewnixpkgs-wayland overview Automated, pre-built, (potentially) pre-release packages for Wayland (sway/wlroots) tools for NixOS (**nixos-unstable** channel). These packages are auto-updated to the latest version available from their upstream source control. This means this overlay and package set will often contain **unreleased** versions. Community chat is on Matrix: #nixpkgs-wayland:matrix.org. We are not on Libera. Started by: **@colemickens** and co-maintained by **@Artturin** (🙏). • overview • Usage • Binary Cache • Continuous Integration • Flake Usage • Install for NixOS (non-flakes, manual import) • Install for non-NixOS users • Packages • Tips • General • - Nvidia Users • Development Guide Usage Binary Cache The Cachix landing page for shows how to utilize the binary cache. Packages from this overlay are regularly built against and pushed to this cache. Continuous Integration We have multiple CI jobs: • Update - this tries to advance nixpkgs and upgrade all packages. If it can successfully build them, the updates are push to master. • Advance - this tries to advance nixpkgs without touching the packages. This can help show when nixpkgs upgrades via has advanced into a state where we are broken building against it. • Build - this just proves that was working against at the point in time captured by whatever is in on . We don't have CI on Pull Requests, but I keep an eye on it after merging external contributions. Flake Usage • Build and run the Wayland-fixed up version of OBS-Studio: • Build and run : • Use as an overlay or package set via flakes: Install for NixOS (non-flakes, manual import) If you are not using Flakes, then consult the NixOS Wiki page on Overlays. Also, you can expand this section for a more literal, direct example. If you do pin, use a tool like to do the pinning so that you don't forget and wind up stuck on an old version. You could write that to a file next to your and then use it like so: Install for non-NixOS users Non-NixOS users have many options, but here are two explicitly: • Activate flakes mode, then just run them outright like the first example in this README. • See the following details block for an example of how to add as a user-level overlay and then install a package with . • There are two ways to activate an overlay for just your user: • Add a new entry in ~/.config/nixpkgs/overlays.nix ~/.config/nixpkgs/overlays/nixpkgs-wayland.nix nixpkgs-wayland nix-env home-manager sway obs sway $HOME/.config/sway/config sway exec sway nix develop ./main.nu ./main.nu build nix-eval-jobs ./main.nu advance main build ./main.nu update main build build nixpkgs-wayland nix develop -c ./main.nu update`