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. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
