Linked by Thom Holwerda on Mon 18th Aug 2008 23:33 UTC, submitted by Charles Wilson
Thread beginning with comment 327277
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: FHS creates complexity beyond naming conventions ..
by hobgoblin on Tue 19th Aug 2008 05:44
in reply to "RE: FHS creates complexity beyond naming conventions .."
the filesystem is.
the structure is like this:
/Programs/bash/version-number/"bin and friends"
inside /Programs/bash there will be a symlink called Default that point to one of the version-number dirs.
that Default symlink again is the target for the symlinks found under /System/Links. (the subdirs of Links is the basis for the compatiblity symlinks btw)
note that at any given time you can specifically call on one of the bash versions by entering the full path, like say /Programs/bash/x.y.z/bin/bash.




Member since:
2008-08-19
Not entirely true. It might keep the files separate - but then it goes and symlinks everything back into the old locations for compatibility with the rest of the world. The Gobo package management tools may have an easier job of tracking which files belong to a package, but they're in just as big a mess maintaining a tree of symlinks. If two versions of Bash are installed side-by-side, something presumably is tracking which one is the default...