J Leslie Turriff via tde-users wrote:
Correct. But for some reason I can't
imagine, I linked the wrong thing.
:-)
I missed this thread, but why don't you build a simple debian package?
If it were to be installed in custom directory, I found out that a kind of
isolation is the best approach.
I use /opt/custom and compile/install in /opt/custom/<application>
Then I add to the global or users PATH /opt/custom/<application>/bin
I also found out that creating /opt/custom/<application> and chown to a
users and compiling/installing with that user prevents from broken
installers. The method never failed, although in recent years I have
reduced the applications there to absolute minimum in favor to debian
packages.
Because
#1 Package bulding is not in my repertoire, and
#2 debian packages don't help much on an RPM-based system. :-)