It has been brought to the Mother's attention that some people don't like theway our FC host tools are designed to be installed under /opt/freecalypso asopposed to some standard location like /usr/local, and that some people havebeen patching our Makefiles and code to move our installed binaries (and perhapssome of the support files as well) to other locations which they like better.PLEASE DON'T DO IT, especially if you are making a package or a build or setupor install script to be used by more than just you. FC host tools are a verycomplex package with a lot of interrelations between different tools, manytools in our suite internally invoke other tools by their /opt/freecalypso/binabsolute pathnames, some tools are designed to be invoked both by human usersand by other tools (rvinterf is a prime example), and there are many supportfiles used by various tools. If you try to outsmart the Mother and change theinstall location to something other than what I designed it to be, you willinevitably break something, and you probably won't notice the breakage becausea typical casual user only uses a very small subset of our tools. Furthermore,if you move the install location, you will certainly break our variousadditional tools which are not included in the core FC host tools package butare meant to be installed on top of it, as all of them expect and require the/opt/freecalypso directory hierarchy described in doc/opt-freecalypso-tree.If your goal is to have our installed binaries accessible with a standard PATHwithout adding /opt/freecalypso/bin to it, the correct solution is to list thebinaries installed in /opt/freecalypso/bin and make a symlink to each of thesebinaries from /usr/bin or from /usr/local/bin or from wherever you like. Usesymlinks, don't move the binaries themselves! If you move the actual binaries,you will break those tools which internally invoke other tools, which we do alot.If you still dislike the whole idea, consider the way Firefox does it: officialrelease binaries from Mozilla are meant to be installed under /usr/lib/firefoxor /usr/lib/firefox-$VERSION, the stuff inside that directory looks nothing likeFHS, it is private to Firefox just like our /opt/freecalypso directory hierarchyis private to FreeCalypso, and the user makes one symlink from /usr/bin/firefoxto /usr/lib/firefox-$VERSION/firefox or wherever the full complex packageresides. If you can live with Firefox and other major application packageshaving their own non-FHS private directory trees, you can surely live withFreeCalypso doing the same.Why did we make our prefix /opt/freecalypso and not /usr/lib/freecalypso or/usr/local/freecalypso? Because there are many, many places where the fullabsolute pathname needs to be typed, and the location we chose is the shortestamong other sensible options.Anyone who is going to make binary packages of our FC host tools (presumablyfor use on systems on which compilation from source is difficult) and wishes tohave their packaging officially endorsed by the upstream MUST follow theseguidelines:* The complete set of tools and support files MUST be included as if one built and installed our package from the official source, without omitting or breaking any part which you might consider unimportant.* Everything MUST be installed under /opt/freecalypso exactly as designed by the Mother; symlinks to binaries under /opt/freecalypso/bin from a more user- friendly location may optionally be included.