The interactivity check creates a couple of issues (like #27), and given that brew is already at the lower priority in the user $PATH, it should be fine to run like this
Brew only actually works with the prefix of /home/linuxbrew/.linuxbrew,
not the fedora-ostree specific /var/home. This should be set correctly
for systems (potentially systemd-sysupdate based systems) that choose to
not include /var/home, but instead use the standardized /home directory.
Signed-off-by: Hec <hec@heccraft.com>
This file creates 3 directories:
- /var/lib/homebrew
- /var/cache/homebrew
- /var/home/homebrew
The first 2 directories seem entirely useless. Grepping through the
entire homebrew codebase for mentions of those 2 directories nets
absolutely nothing.
The /var/home/homebrew directory here is problematic. It creates the
directory with the owner set to uid/gid 1000. This breaks usecases where
the user wants to change the owner of this directory, such as for
systems that utilize systemd-homed, or systems that utilize a new
project called brew-proxy.[1]
The directory is already created by brew-setup.service, and it does not
need to be created outside of that. If a user deliberately removes this
directory, it should not be recreated as an empty directory.
[1]: https://codeberg.org/HastD/brew-proxy
Signed-off-by: Hec <hec@heccraft.com>
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
This will avoid issues such as `systemctl` coming from `systemd` on
brew, `qdbus`, `dbus`, and honestly many others that we dont really
know. Also would prioritize things on the image whenever possible
Signed-off-by: Tulip Blossom <tulilirockz@outlook.com>
- 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
