On Sun, May 24, 2009 at 3:18 AM, John Summerfield <[email protected]> wrote:
> Why do you think you should install to /opt2? I can't for the moment think > why I would, but if I did I most likely create an rpm that contains that > directory structure, and list it as a prereq for everything else I was > going to build & install there. > > However, this isn't a very standard way of doing things. <snip> Thanks to everyone for the comments. Shortly before John's above email arrived, I came to his same conclusion. Our site has accumulated lots of non-standard practices over the years such as storing applications in atypical places. My post mentioned /opt2 just to make my situation comprehensible -- the actual setup is far more convoluted. I decided to finally do things the right way after reading the Filesystem Hierarchy Standard: http://www.pathname.com/fhs/ Now I'll just just /opt. If I had stuck with /opt2, I would have created an "addons" RPM which owned that directory and made other local customizations. Matt
