> Ah, you was so close :) "unset" command was introduced
> beginning with 2.6.3
> Is any way to update to cmake 2.6.3 or later? Current cmake
> port is designed 
> for the future, i won't support ancient versions of cmake
> (current is 2.8.4, 
> 2.6.2 was released in 2008).

I will try, but I don't think that is right. :(

Not to argue, but that is an awful definition of "ancient." :) You say 2.6.2 is from 2008? I will never define that as ancient. That is one of the problems with free/libre software. The train is always moving at break-neck speed with little or no backwards compatibility. :(

Another argument for using older distros that remain supported by the distro maintainers is they tend to run better and have better support for older hardware. Older hardware is a target for Trinity users whereas KDE4 is not.

I'm trying to build packages on Slackware 12.2, a known good foundation that I built packages last autumn. I intend to start trying to build on subsequent Slackware releases, but first I want to build a handful of packages in a known good environment to test cmake and the many svn changes since then.

I don't pretend to understand what is involved, but sure would be nice to build with 2.6.2. Many people still use slightly older distros. Considering that "long-term support" for many distros is three years or more, Slackware 12.2 is only two years old. I should be able to build Trinity on Slackware 12.2 with a cmake version that is only two years old.

Perhaps the root problem here is that tqtinterface no longer can be built with autoconf. I should be able to build Trinity entirely with autoconf on a slightly older distro.

How will updating cmake affect the final packages? That is, if I update the cmake package in Slackware 12.2, will that affect users who install the Trinity packages on 12.2, which was released with cmake 2.6.2?

Darrell