TTY is an interactive shell and when you launch your desktop this way
(not through a Display Manager) then the linuxbrew directory in the
$PATH will be inherited and in turn causes non-interactive shells to
have linuxbrew, this is noticeable in things like krunner and rofi.
It's still at the end of the $PATH so system binaries will have
precedence and it should not break anything.
Having brew on the TTY in $PATH is useful so I think this is a fine
workaround. I don't see a way for us to not make it so that this
specifically is not inherited to the desktop.
This fixes the cosmetic issue of it being present twice in $PATH.
This was brought up in [1].
[1]: https://github.com/ublue-os/brew/issues/24#issuecomment-4574594563
- Add detailed overview of what the repository provides
- Document all included components (tarball, services, shell integration)
- Add practical examples for using in custom bootc images
- Include basic, advanced, and Universal Blue integration examples
- Document build process and runtime behavior
- Add environment variables and file locations reference
- Include systemd service details
- Add troubleshooting section for common issues
- Document contribution guidelines and related projects
