Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14687 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-10-04 10:23 -0400 |
| Last post | 2018-10-04 10:23 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Auto-update program cache feature Chet Ramey <chet.ramey@case.edu> - 2018-10-04 10:23 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-10-04 10:23 -0400 |
| Subject | Re: Auto-update program cache feature |
| Message-ID | <mailman.1704.1538663003.1284.bug-bash@gnu.org> |
On 10/3/18 4:45 PM, Jeffrey Walton wrote: > Hi Everyone, > > I noticed a fair number of new Linux users have trouble with stale > program caches. Users install a package from a package manager or > sources and then are confused when the new package is not used. They > do not realize they need to run 'bash -r'; and most don't know where > to begin searching. OK, let's consider this. There are three cases: 1. A new program gets installed with the same name as an existing one, in the same directory. 2. A new program gets installed with the same name, but in a different directory in $PATH (and before the existing one). 3. A new program gets installed with a new name. (I'm putting aside the program deletion case.) You're saying that the seond scenario is most common, and common enough that we should develop a complex solution for it? I'd have to see more data before I'd accept that. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web