Default configuration for Fedora Sway Spin
https://docs.fedoraproject.org/en-US/fedora-sericea/configuration-guide/
- QML 31.8%
- Shell 26.8%
- Python 18.3%
- CSS 15.5%
- Makefile 7.6%
There are issues with escaping and arguments splitting that we're unable to solve at the moment. For example, `.desktop` files with whitespaces and other characters treated specially by Sway in the `Exec=` field are known to be broken[1][2]. Removing `-run-command`/`-run-shell-command` costs us pid-based workspace assignment. I.e. the applications that take a while to load will appear on the current workspace instead of the one they were launched on. That is at least partially mitigated by the fact that the app will inherit `XDG_ACTIVATION_TOKEN` and `DESKTOP_STARTUP_ID` variables created for for `exec rofi` command with a default lifetime of 30s[3]. But not all applications or UI frameworks support that. This could be revisited later, once we have a solution that correctly escapes the command to pass it through `swaymsg exec`. [1]: https://i3wm.org/docs/userguide.html#exec_quoting [2]: https://github.com/swaywm/sway/issues/5931 [3]: https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/0.16/types/wlr_xdg_activation_v1.c#L361 |
||
|---|---|---|
| scripts | ||
| sddm | ||
| sway | ||
| swaylock | ||
| waybar | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| rpkg.conf | ||
| rpkg.macros | ||
| sway-config-fedora.spec.rpkg | ||
Sway config
Sway config is split to 2 parts:
sway/config— is the main config to be installed to/etc/sway/config. Some light changes are applied, such as removing things we want to override later (bar, launcher, etc.).sway/config.d/*.conf— is a set of small self-contained configuration snippets with each containing the description and the list of required packages. Will be installed as/usr/share/sway/config.d/*.confand loaded by default.
Upstream config changes sync
The process described below should used to update the configuration for a new upstream project release. The goal is to limit merges to changes since last release and to simplify tracking our local modifications.
- Switch to the
upstreambranch - Overwrite the configuration file with an updated one
- Do any pre-processing if necessary, e.g. replace variables, paths or anything else upstream buildsystem does before installing the file.
- Commit changes, specifying the upstream release or tag in the commit message. Example:
sway: sync config with upstream release 1.8 - Switch to the
fedorabranch and merge changes fromupstream - Update required project version in the RPM spec as necessary.