On Wednesday 16 September 2020 12:22:05 deloptes via tde-users wrote: > 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. > > > I was thinking of doing this myself, but I obviously am not really a tech person, compared to most of the other folks on this mailing list. Funny thing, though, people out in the "real world" (you know the place) often eem to imagine that I am a blackhat cracker who can bring down the government with a few command-line tricks. (I have no such illusions.) Once I get the steps for installation from source packages in order, I wanted to create deb packages, at least for myself. It would be nice to get them hosted somewhere, as I dislike having to use source packages -- although I know some geeky friends who swear by this method over using deb, rpm, yum or other packages. So, if I follow what you say, installing to /opt/custom/ instead of /usr/lib/ ? Bill ____________________________________________________ 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
