Don't know what bigred's reasoning is, but I would argue that his approach is a better approach from a long-term user perspective.You have provided a method that (probably) does what the poster needs. But others think there is a shorter and easier-to-use method. You clearly think that there is a reason why your version is better, but now refuse to elucidate. So, yes it is your problem. Please explain.I'm sorry if you don't get it. But that's not my problem.
Yes, dumping the 2 envar's into .bashrc is easier, but thinking about the upcoming move that most desktop users will be making to trixie and beyond, it's cleaner to implement it as bigred has suggested.
If a user installs this on their pi today and then carries it along to all their inevitable new Pi's, every one of them could easily end up with these envar defs in their .bashrc, even when they aren't needed.
Then, when the user becomes a grizzled old user like some of us, they'll look at their .bashrc and ask themselves WTF is this?!?
OTOH, with bigred's approach, those systems won't have (admittedly small) extra baggage running every time they login, and they are easily able to bring them forward by copying their whole ~/bin directory.
Then, instead of GOU looking at their .bashrc, they can review the contents of their ~/bin directory
Statistics: Posted by bls — Mon Feb 17, 2025 6:02 pm