No, each Trinity package must be installed before the next can be built. The include files have changed dramatically from KDE3.5.10 due to the new features (e.g. the new low level libkrandr library) and also due to the TQt conversion.
Seems then that in my prerequisite checks I should test for the installation of stock 3.5.10 packages?
Should each subsequent package build script test that the previous Trinity packages are installed?
Are there any special files I can query to ensure the Trinity packages are installed and not the stock packages?
The only thing I can think of is to check the KDE version number; if it is greater than or equal to 3.5.11 then Trinity is installed.
Slackers tend to be DIY types but I think providing warnings or checks might be prudent.
WDYT?
Probably a good idea; I don't have the time at the moment to pursue it further but if you come up with a reliable method for doing this I would be willing to look at it and commit it to SVN.