On Tue, Jan 08, 2002 at 12:53:41PM +0530, newlxuser wrote: > Date: Sat, 5 Jan 2002 12:03:36 +0530 > From: USM Bish <[EMAIL PROTECTED]> > > >Don't know what is the point of the exercise ! Why have three > >binaries (obviously doing the same thing) installed together? > > I had installed RH6.2 in a office, some-time back. Every- > thing was running fine, & all were happy to use the 'Joe', > for their "text-only" office correspondence, due to it's > close proximity to WordStar ! > > But alas ! Six months back, one of the office's "smart" > executice brought a "Desi" text-editor from some-where & > forced me to install it in their PC. So-far-so good ! The > editor has function keys to do some Open-Save-Copy-Paste > etc general functions. It was version 1.0 . ( I did'nt > find any-thing worth-while in it.) > > A month back the executive brought version 2.0 of the same > editor with some enhanced functions. But I was shocked to > know (after installing the package), that the dumb > programmer has changed some of the common function keys > and assigned some diff new tasks to these keys. > > The 2 clerks in the office are reluctent to use the new > version since they are used to the old one. And the exe- > cutive is bent on installing the new version. Looking at > the "bechaara" clerk's agony, I am trying to find out the > sol'n, so that both the packages can be used at a time ! > > The problem is, both the packege's default installation > directory is under \user\"desi" . > ( And I do not have the source code for the package. I > will be glad to have my hands on the dumb "creator" to > "pour" some sense in his brain - if he has it at-all. ) >
This is NOT a case of the same app. Two versions even with the same app name ARE different. The example below for installing ProgA ver 1 and ver 2 both having the same name Prog is being shown as an example: First move the old version to a new name #mv Prog ProgA-1.0 Then install the new version of ProgA. Once done, do #mv Prog ProgA-2.0 For most folk who want to use ProgA (version 2), do: #ln -s ProgA-2.0 Prog (assuming both are on default path) Using the command Prog will normally bring out Ver 2.0 .. For those still wanting to use Ver 1.0, tinker their local config in .bash_profile alias Prog='/path/to/ProgA-1.0' Note: settings of local alias takes precedence over path There is nothing technical in above. Pure logic. > > >i) Last word of advice : DO NOT do above. If you want to vary > > with the default binary for your distro, at best compile > > from the developer's tarball. > > And what, if we do not have the original tarball ? > It is the developer's tarball that I am talking about and NOT "original" tarball. For RH, package-src-ver.rpm would be consi- dered an original tarball, but it is NOT the developer's tarball Developer's tarballs need to be downloaded from the net. > > >The "group" must be a bunch of adventurous kids to even think > >of such gimmicks, for no additional benefit :-( > > Sorry ! These are stuborn "elders" battling for the sake of > prestige only! ;-( > You mean REAL KIDS ! That's about the toughest bunch to handle ! HTH Bish -- : ####[ Linux One Stanza Tip (LOST) ]########################### Sub : What all is mounted ? LOST #098 To know all mounted devices, do : cat /proc/mounts Example below is to check for a mounted floppy from console or from script : cat /proc/mounts | grep "/dev/fd0" ####<[EMAIL PROTECTED]>######################################## : _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
