Packaging

System76’s COSMIC Desktop Environment—written from the ground up in Rust—is one of the most exciting developments in the Linux desktop ecosystem. Built for modern Wayland composition, modularity, and high-performance UX, it has captured the attention of desktop enthusiasts across distributions.

However, for users running Debian Testing or Debian Unstable, getting COSMIC onto their machines traditionally presents a steep hill to climb. The official upstream codebase consists of dozens of independent repositories (cosmic-comp, cosmic-panel, cosmic-applets, cosmic-settings, cosmic-files, and more) along with hundreds of Rust crate dependencies. Packaging each component individually according to strict Debian policy involves filing dozens of ITPs, waiting through NEW queue processing, and managing endless dependency updates.

When writing packages for Debian, one of the biggest problems is determining the packages to be put in Build-Depends

Sometimes, a single dependency in Build-Depends ends up building the package successfully on your machine while it fails on other machines. This is where pbuilder is really handy. It allows you to have bare minimal Debian OS releases, to which you can pass the package to build. It downloads the Build- Depends and then does a build in the clean Debian build environment. Now if you’ve provided incomplete Build-Depends, your build will fail.