> Where is KDE4 installed to on a arch linux install?
> 
> Oh look it installs into /usr just where tde should also
> install to .
> 
> The issue is that because of conflicts, tde can not be
> installed to /usr so the arch devs simply can not install it
> there.
> Since it is _not_ installed from a distro... I believe that
> LSB states it is a locally installed package that should go
> into /usr/local.
> After all it is local to the boxen in question.
> I have kde-3.5.10 and tde 3.5.13 installed on a single
> slackware-12.2 boxen with tde installed to /usr/local. Both
> easily work.

The root issue here is not where each individual wants to install Trinity, or where upstream distro maintainers and packagers should install Trinity, but to ensure there never is a conflict with other packages.

The sole thorn in our side is and always will be KDE4. Anybody packaging Trinity for a distro that includes KDE4 needs to work around where KDE4 gets installed. If the upstream maintainers are installing KDE4 to /usr, then Trinity has to be installed elsewhere. If the upstream maintainers are installing KDE4 to someplace other than /usr, then Trinity can be installed to /usr.

Anybody who controls the distro and decides that KDE4 is not an option can install Trinity to /usr. Most of us do not control those decisions.

One thing is clear: as a team we do a poor job testing Trinity for conflicts with KDE4. I don't care what KDE4 developers think about Trinity, but I don't want them accusing us of sloppy programming or packaging. Testing Trinity for potential KDE4 conflicts needs a much higher priority for all of us. That does not mean installing to /opt or /usr/local merely to avoid conflicts in /usr/bin and /usr/lib, but actually testing both desktops in real time.

Build your packages where you want according to your distro or personal guidelines, but let's focus on the real challenge of producing a robust Trinity. :)

Darrell