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
6 lines
837 B
XML
6 lines
837 B
XML
<svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" fill="context-fill" fill-opacity="context-fill-opacity">
|
|
<path d="M11.72 6.586c-.799.537-1.787 1.167-3.303 1.422a.5.5 0 0 0-.418.492v2.564c0 2.288 1.648 4.08 3.822 4.902a.5.5 0 0 0 .356 0c2.174-.822 3.822-2.614 3.822-4.902V8.5a.5.5 0 0 0-.419-.492c-1.514-.255-2.503-.885-3.302-1.422a.5.5 0 0 0-.56 0zm.28.992c.716.47 1.69.982 3 1.281v2.205c0 1.741-1.23 3.108-3 3.848-1.77-.74-3-2.107-3-3.848V8.86a9.083 9.083 0 0 0 3-1.28z"/>
|
|
<path d="M6 0C4.901 0 4 .901 4 2v10c0 1.099.901 2 2 2h1.836a5.373 5.373 0 0 1-.488-1H6c-.558 0-1-.442-1-1V2c0-.558.442-1 1-1h6c.558 0 1 .442 1 1v3.865c.203.139.748.48 1 .592V2c0-1.1-.902-2-2-2H6z"/>
|
|
<path d="M3 2.271C2.404 2.619 2 3.265 2 4v8.5C2 14.427 3.573 16 5.5 16h4.252a7.236 7.236 0 0 1-1.154-1H5.5A2.492 2.492 0 0 1 3 12.5z"/>
|
|
</svg>
|