Luigit
repositories / dotfiles

dotfiles

bugabingas dorkfiles

owned by admin

pi/agent/skills/optional/quickshell/references/packaging.md

Raw
Rendered preview

Installation and packaging

Package availability and build dependencies change. Use the install guide matching the desired Quickshell release:

https://quickshell.org/docs/v<version>/guide/install-setup/

For an existing machine, inspect before changing anything:

qs --version
qs --help

Prefer the distribution's supported package path unless the user asks for a source build or another packaging model. Do not add blanket package pinning, source-build scaffolding, compatibility branches, or version gates. If multiple versions are an explicit requirement, define the supported versions and test each one.

Editor setup

Follow the installed guide for qmlls setup. A .qmlls.ini file contains machine-specific paths and should not be copied as portable configuration.

Troubleshooting order

  1. Capture the exact qs version and full diagnostic output.
  2. Verify the QML import paths and installed modules.
  3. Check the matching official type page for every unresolved symbol.
  4. Distinguish a static or load failure from a mapped-surface, compositor-protocol, or service failure.
  5. Reproduce runtime behavior only in an isolated environment when the configuration can claim desktop protocols or services.
# Installation and packaging

Package availability and build dependencies change.
Use the install guide matching the desired Quickshell release:

```text
https://quickshell.org/docs/v<version>/guide/install-setup/
```

For an existing machine, inspect before changing anything:

```sh
qs --version
qs --help
```

Prefer the distribution's supported package path unless the user asks for a source build or another packaging model.
Do not add blanket package pinning, source-build scaffolding, compatibility branches, or version gates.
If multiple versions are an explicit requirement, define the supported versions and test each one.

## Editor setup

Follow the installed guide for `qmlls` setup.
A `.qmlls.ini` file contains machine-specific paths and should not be copied as portable configuration.

## Troubleshooting order

1. Capture the exact `qs` version and full diagnostic output.
2. Verify the QML import paths and installed modules.
3. Check the matching official type page for every unresolved symbol.
4. Distinguish a static or load failure from a mapped-surface, compositor-protocol, or service failure.
5. Reproduce runtime behavior only in an isolated environment when the configuration can claim desktop protocols or services.