Really?
trinity is not software locally installed by the local system admin?
Right now it is - but very soon it will be installed from mirrors, via the package manager; users are expecting /usr/local to be stuff installed by them not the package manager
/usr/local IS for software installed after the base distribution. Since trinity is not installed by default in a lot of distros, onw should place that sofware into /usr/local
Just because it is not installed by default doesn't mean it shouldn't operate as a normal package.
What will you do when it is or how is distros supposed to pick it up if it won't work when installed into /usr?
That is for upstream to solve. as packagers we are just here to package. Trinity is continuing to work on the renaming effort - until it is finished I do not want any conflicts.
Installation into /usr _should_ be the goal not playing with installation into /opt.
Any way it's not an issue with me as I will continue on.....onward on my own path installing into /usr/local, since it is your way or no way.
I have offered many a time to have you join up and you consistently refuse.
/usr/local simplifes the install and keeps it separate from the distro stuff (Arch soon to be my own scratch built ) and does not interfere with QT4 and KDE4 and without all the mumbo jumbo associated with the install into /opt. The build goes better and the install goes better.
Have you even bothered to read the arch package guidelines which so profess like a holy book?
"Packages should never be installed to /usr/local"
"/opt/{pkg}: Large self-contained packages such as Java, etc."
I consider trinity a large self contained project.
Furthermore /opt/ is a bit more of a saner solution because it helps keep everything seperate - this is something I think is good. especially while packages are still in beta stages.
When the time comes to merge into the archlinux official packages, we can move it where they wish. I do think they will prefer /opt/
Calvin Morrison