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%
We recommend use of application launcher in installation instructions but Anaconda won't start until xhost application is started. It's already solved by starting xhost app in ~/.bashrc, however, that won't work for a launcher because it's not sourcing ~/.bashrc. To solve this, start xhost by Sway configuration file on Live. |
||
|---|---|---|
| doc | ||
| 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.