>> > 3. Finally, the RPMs are not compliant with Linux Filesystem Hierarchy >> > Standard (http://www.pathname.com/fhs/), concerning where they install >> > files. My understanding is that everything should be installed into >> > /usr/lib/dx (rather than /usr/local/dx, /usr/dx, or /dx), except that >> > the executable script dx should be moved or copied into /usr/bin/dx, >> > and the man page should be moved or copied into /usr/man/man1/dx.1. >> > >> > Thanks for your work on the opendx RPMs. -- Doug Arnold >> >> I had /usr in my previous rpms. However, I prefer not to mess around with >> /usr directory therefore choose the /usr/local again. It is my personal >> opinion, >> not to install user applications in /usr directory, instead install it in >> /usr/local >> to keep the system binaries separate from user applications.
In that case, I would vote for putting everything in /usr/local/lib/dx rather than /usr/local/dx. And the script in /usr/local/bin/dx and the man page in /usr/local/man/man1/dx.1. >> Well, that is where users would run into troubles when they prefer >> precompiled binaries. Every developer has its >> own prefereneces for compilers. In my opinion GCC 2.95.2 is a lot better >> compiler then egcs-1.1.2. RedHat was distributing egcs-1.1.2 upto version >> 6.1 >> because there were some Linux kernel compilation issues (that is what I >> guess). >> But GCC-2.95.2 now compiles Linux Kernel 2.2.x and 2.3.x. Beside, I use >> GCC-2.95.2 >> also on Windows and prefer to have same compilers on Linux so I can have my >> development tools on Linux and Windows in sync. Fair enough. Fortunately, as I said in my follow-up message. There is an easier way, just to install the new libstdc++ without deleting the older one. Again, thanks. -- Doug
