Once upon a time, Gentoo users could have multiple versions of KDE
installed without any compatibility problems by using the following prefix
system:
- */usr/kde* as the main dir
- /usr/kde/3.5 as the dir for the 3.5 install
- /usr/kde/3.4 as the dir for the 3.4 install
Now, I don't know how it handled the paths in the environment but
everything was transparent and worked great. One would just select which
version to boot on KDM and everything would work fine. I think the session
script was used to set up the proper paths but I'm not sure.
Perhaps it is worth looking into a similar scheme for trinity, where *
/usr/trinity* could be used as the main folder - as was mentioned on a
previous e-mail by Robert.
Best regards,
Tiago
On Fri, Nov 25, 2011 at 9:27 PM, Timothy Pearson <
kb9vqf(a)pearsoncomputing.net> wrote:
If the system
administrators do this change, how will we accommodate
Trinity to it?
Fedora is doing it; openSUSE is having an argument about if this is good
or not.
Gentoo had a discussion on this, I think.
Should this be treated like a simple "let's move to /usr/local" or has
the renaming allowed us to install side by side with KDE4 without the
use of /opt?
We have not renamed everything--we would still conflict with KDE4 due to
applications such as konsole and kwrite.
Not knowing too much about the standard directories on RPM systems, would
it be possible to install to /usr/trinity ?
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting