I wish that it could just be as easy as running a few Cargo commands. Though, I have not taken a look at how the project is made/programmed or anything. I wish it could be as simple as
We use casey/just as a better makefile alternative. Shared system library dependencies will be listed in the debian/rules file, and most things should compile and install with just && sudo just install.
It’s already packaged on multiple distributions, albeit in an unofficial capacity. If you are on Pop!_OS, you can install the cosmic-session package today, then enable Wayland in the gdm3 config. We have an apt-manage tool which you can use to add development branches. A popdev branch is created for each branch on GitHub pushed by a team member. Which can be useful to quickly add a branch to validate a fix by a developer.
I wish that it could just be as easy as running a few Cargo commands. Though, I have not taken a look at how the project is made/programmed or anything. I wish it could be as simple as
cargo buildcargo install(or similar command)We use casey/just as a better makefile alternative. Shared system library dependencies will be listed in the
debian/rulesfile, and most things should compile and install withjust && sudo just install.That’s very nice to hear. So it’ll be easy to get up and running with Cosmic even if I’m on a different distribution?
It’s already packaged on multiple distributions, albeit in an unofficial capacity. If you are on Pop!_OS, you can install the
cosmic-sessionpackage today, then enable Wayland in the gdm3 config. We have anapt-managetool which you can use to add development branches. A popdev branch is created for each branch on GitHub pushed by a team member. Which can be useful to quickly add a branch to validate a fix by a developer.