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
1.1 KiB
XML
5 lines
1.1 KiB
XML
<svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" fill="context-fill" fill-opacity="context-fill-opacity">
|
|
<path fill="context-stroke" d="M8.5 1c-.397 0-.78.158-1.061.44L4.878 4H3.499a2.511 2.511 0 0 0-2.5 2.5v3c0 1.372 1.128 2.5 2.5 2.5h1.379l2.561 2.561a1.537 1.537 0 0 0 1.635.325c.51-.212.925-.76.926-1.385v-2.6a1.516 1.516 0 0 0 1.582-.34l.44-.44.439.44a1.516 1.516 0 0 0 2.12 0 1.515 1.515 0 0 0 0-2.121L14.143 8l.44-.44a1.515 1.515 0 0 0 0-2.12 1.516 1.516 0 0 0-2.121 0l-.44.44-.44-.44a1.51 1.51 0 0 0-1.06-.44c-.176 0-.353.034-.522.096V2.498A1.506 1.506 0 0 0 8.5 1z"/>
|
|
<path d="M8.5 2a.5.5 0 0 0-.353.146L5.291 5.002H3.5C2.677 5 2 5.678 2 6.5v3c0 .822.678 1.5 1.5 1.5h1.793l2.854 2.854A.5.5 0 0 0 9 13.5v-11a.5.5 0 0 0-.5-.5zM8 3.707v8.586l-2.146-2.146A.5.5 0 0 0 5.501 10h-2a.493.493 0 0 1-.5-.5v-3c0-.282.217-.5.5-.5h2a.5.5 0 0 0 .353-.146zM10.521 6a.5.5 0 0 0-.354.853L11.315 8l-1.146 1.146a.5.5 0 0 0 .707.707l1.146-1.146 1.146 1.146a.5.5 0 0 0 .707-.707L12.728 8l1.146-1.146a.5.5 0 0 0-.707-.707L12.02 7.292l-1.146-1.146A.498.498 0 0 0 10.52 6z"/>
|
|
</svg>
|