mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-11 12:27:50 +01:00
Krzysztof kuhy Rudnicki
4f2b0ccdf7
Two levels of pure taxonomy carrying no information, and a 2-directory
cap leaves no room for them. Categories now sit directly under
linux_configuration/: features, fixes, utils, misc, fresh-install,
installers, diagnostics, gaming, boot_recovery, periodic_background, lib,
meta, tests. A script's own lib/ and tests/ are exempt from the cap, so
those stay put.
Depth violations 248 -> 139; roughly 40 of the remainder are inside
digital_wellbeing and hosts, deferred until the guard-lib repoint.
The moves are the easy half. What breaks is every path that counted
levels, and three classes of it had to be found by resolving paths rather
than reading diffs:
- 52 relative `source` lines for lib/common.sh and lib/android.sh. The
correct prefix differs per file: 40 were ../../ and 12 were ../../../,
so a blanket replace would have fixed one set and broken the other.
- REPO_ROOT in 7 fixes/lib/tests harnesses and setup_syncyomi_guard.sh,
each walking up four levels from a directory now two levels shallower.
This caused a real regression -- the fixes suite went red with
"log_warn: command not found" -- caught by running it and comparing
against the pre-move baseline worktree.
- conftest.py's sys.path entries, which took the pytest gate down with
14 collection errors, and the `# shellcheck source=` directives, which
took shellcheck down with SC1091.
16 symlinks in $HOME broke, including the entire i3blocks bar. All
repointed, and cpu_monitor/memory/disk/time/volume were run to confirm
they emit real output rather than merely resolving.
Verified: 1798 tests pass at 100% coverage, 8 of 9 lib/tests suites pass
(the ninth needs the coverage jail, identically at baseline), pre-commit
is clean, and the two untracked secret configs are still ignored after
their gitignore paths changed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp
67 lines
1.6 KiB
Markdown
67 lines
1.6 KiB
Markdown
# Package Lists
|
|
|
|
This directory contains package lists for the fresh install script:
|
|
|
|
- `pacman_packages.txt` - List of packages to install via pacman
|
|
- `aur_packages.txt` - List of AUR packages with their repository URLs
|
|
|
|
## Format
|
|
|
|
### pacman_packages.txt
|
|
|
|
One package name per line:
|
|
|
|
```
|
|
package1
|
|
package2
|
|
package3
|
|
# This is a comment and will be ignored
|
|
# Another comment
|
|
```
|
|
|
|
### aur_packages.txt
|
|
|
|
Package name and repository URL separated by space:
|
|
|
|
```
|
|
package-name https://aur.archlinux.org/package-name.git
|
|
another-package https://aur.archlinux.org/another-package.git
|
|
# This is a comment and will be ignored
|
|
# Another comment
|
|
```
|
|
|
|
**Note**: Lines starting with anything other than lowercase letters (a-z) or digits (0-9) will be ignored as comments. This includes lines starting with `#`, spaces, uppercase letters, or special characters.
|
|
|
|
## Usage
|
|
|
|
The `main.sh` script will automatically read from these files:
|
|
|
|
- Pacman packages will be installed via `pacman -Sy --noconfirm`
|
|
- AUR packages will be built and installed via the `install_from_aur` function
|
|
|
|
## Modifying Package Lists
|
|
|
|
To add or remove packages:
|
|
|
|
1. Edit the appropriate `.txt` file
|
|
2. For AUR packages, ensure the format is correct (package-name followed by space and URL)
|
|
3. You can add comments by starting lines with `#` or any non-alphanumeric character
|
|
4. Save the file - the script will automatically pick up changes on next run
|
|
|
|
### Comments
|
|
|
|
You can add comments to organize your package lists:
|
|
|
|
```
|
|
# Essential packages
|
|
git
|
|
vim
|
|
|
|
# Development tools
|
|
gcc
|
|
make
|
|
|
|
# Optional packages (commented out)
|
|
# some-package-i-might-want-later
|
|
```
|