|
|
Subscribe / Log in / New account

Program names and "pollution"

Program names and "pollution"

Posted Apr 3, 2019 0:01 UTC (Wed) by KaiRo (subscriber, #1987)
In reply to: Program names and "pollution" by buck
Parent article: Program names and "pollution"

Well, if I put /usr/local/postgres into my $PATH because I use its commands often enough, I end up with the same issue...


to post comments

Program names and "pollution"

Posted Apr 3, 2019 5:23 UTC (Wed) by rsidd (subscriber, #2582) [Link]

Yes but at least it is obvious what package "createuser" belongs to in that case. If you don't add that directory to your path (which, unless you use postgres, you won't), you won't even see it. It won't break scripts, it won't clobber other binaries, the only issue is if there is another "createuser" in some other program's bin directory and for some reason you need to be able to run both -- but it's still better than putting both in /usr/bin.

Seriously, why not do this? Also, I guess newer systems like flatpak and snappy would basically be doing this.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds