giovannino/sway-config-fedora
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Default configuration for Fedora Sway Spin https://docs.fedoraproject.org/en-US/fedora-sericea/configuration-guide/
61 commits 7 branches 11 tags 696 KiB
  • QML 31.8%
  • Shell 26.8%
  • Python 18.3%
  • CSS 15.5%
  • Makefile 7.6%
Find a file
Exact
Aleksei Bavshin 2ae27356aa
 sway: enable floating for pavucontrol window
2023-03-23 00:37:55 -07:00
scripts sway: limit volume boost via helper script 2023-03-23 00:37:54 -07:00
sddm sddm: fix fullscreen command invocation 2023-03-22 22:19:12 -07:00
sway sway: enable floating for pavucontrol window 2023-03-23 00:37:55 -07:00
swaylock sway: add swayidle and swaylock configuration 2022-06-29 07:32:07 -07:00
waybar waybar: sync config with upstream release 0.9.16 2022-12-11 18:49:14 -08:00
LICENSE Update copyright 2022-11-29 20:51:54 -08:00
Makefile Add configs for Live to show install instructions 2023-01-14 20:13:10 +00:00
README.md sway: allow overriding or disabling our configs per user 2022-08-05 06:48:41 -07:00
rpkg.conf Add rpm spec 2022-05-30 21:58:59 -07:00
rpkg.macros rpkg: switch to the current snapshot versioning scheme 2022-12-19 08:10:41 -08:00
sway-config-fedora.spec.rpkg sway: use output power instead of deprecated dpms 2023-03-22 21:34:37 -07:00

README.md

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/*.conf and 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.

  1. Switch to the upstream branch
  2. Overwrite the configuration file with an updated one
  3. Do any pre-processing if necessary, e.g. replace variables, paths or anything else upstream buildsystem does before installing the file.
  4. Commit changes, specifying the upstream release or tag in the commit message. Example: sway: sync config with upstream release 1.8
  5. Switch to the fedora branch and merge changes from upstream
  6. Update required project version in the RPM spec as necessary.