Gabriel Brown
88497826ec
Phase 4: the optional application categories, and the Firefox chrome. Everything Panama installed until now was what every machine gets, which meant a work laptop acquired emulators and a desktop that wanted Steam had to be told about it by hand. The interview now offers the categories in setup/packages/extras/ as a checklist -- gaming, creative, communication, virtualization -- and nothing is preselected, because a default here installs applications nobody chose on a machine whose owner answered a question they thought was about something else. A category is one file, and a category mixes both package managers because the applications do: Steam is in RPM Fusion, Slack publishes only a flatpak. So a bare line is a dnf package and a flatpak: line is a Flathub ID, and one file holds the whole answer rather than splitting each category across two. The menu is read from the directory rather than written down, so adding a category is adding a file. Every name in all four was resolved against the actual repositories before being written down, and the contract re-resolves them -- the point of admitting applications one at a time is that they stay installable, and a typo here fails on somebody else's machine, not this one. Firefox is declared, and its chrome is Edge-Frfox, vendored into config/firefox. sunhat carried that theme with no license and no attribution; it is MIT, and now it says so and says whose it is. It is the only piece of Panama's configuration that does not go to a path this repository chooses. Firefox owns the profile directory, names it with a random salt, and does not create one until the browser has been run -- so link-dotfiles finds or creates a profile and links both halves into it. Both, or neither works: chrome/ is the CSS and user.js sets the preference that makes Firefox read chrome/ at all, without which the theme is a directory of dead files. Two assumptions there were wrong, and the contract exists for both. Firefox has moved to the XDG directories -- the profile root is ~/.config/mozilla/firefox on this build, not ~/.mozilla/firefox, and writing to the wrong one themes nothing and says nothing about it. And -CreateProfile turns out to be non-interactive, so a fresh machine gets the theme on the first install rather than the second. The contract runs link-dotfiles for real against a throwaway home with no profile in it and looks at what came out; it was checked by pointing the search at the legacy path only and watching it fail. Also: the enrolment/enrollment spellings from the last commit are corrected. This repository is US-spelled everywhere else -- color 1131 times against colour never -- and consistency in prose is worth as much as it is in code. Claude-Session: https://claude.ai/code/session_01NvgBuSWB5sE43yWmg21ozj
5 lines
825 B
XML
5 lines
825 B
XML
<svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" fill="context-fill" fill-opacity="context-fill-opacity">
|
|
<path d="M7.5 0c-.647 0-1.204.42-1.412 1H4.5C3.677 1 3 1.677 3 2.5v3.76c.21-.086.723-.213 1-.232V2.5c0-.283.218-.5.5-.5h1.588c.208.58.765 1 1.412 1h3c.647 0 1.204-.42 1.412-1H13.5c.282 0 .5.217.5.5v12c0 .282-.218.5-.5.5h-2.586c.137.34.098.785 0 1H13.5c.823 0 1.5-.678 1.5-1.5v-12c0-.823-.677-1.5-1.5-1.5h-1.588c-.208-.58-.765-1-1.412-1zm0 1h3c.282 0 .5.218.5.5s-.218.5-.5.5h-3c-.282 0-.5-.218-.5-.5s.218-.5.5-.5z"/>
|
|
<path d="M4.5 7A3.508 3.508 0 0 0 1 10.5C1 12.427 2.573 14 4.5 14c.784 0 1.509-.26 2.094-.7l2.553 2.554a.5.5 0 0 0 .707 0 .5.5 0 0 0 0-.707l-2.553-2.553c.438-.585.7-1.31.7-2.094C8 8.573 6.426 7 4.5 7zm0 1C5.887 8 7 9.113 7 10.5S5.887 13 4.5 13 2 11.887 2 10.5 3.113 8 4.5 8z"/>
|
|
</svg>
|