Great news... and I hope things work out so that they can offer Trinity/ Devuan packages. I have been using Devuan and Trinity for the last 6 months with no problems--actually even less problems than I had with Debian. I just upgraded to the latest Devuan release--again with no problems. But, I have found that if you want absolutely no problems with the combination, you should install Devuan and Trinity on a clean system, bare metal so to speak. I did that with the latest RC release and had less configuration issues than I did when I upgraded Debian and Trinity to Devuan and Trinity 14.04 in place. Keith On Fri, May 12, 2017 at 2:17 PM, Dr. Nikolaus Klepp <office(a)klepp.biz> wrote:

this can be entirely solved by *devuan* adding the TDE packages to devuan/testing... and compiling them on their own server farms, signing them with *their* package keys.

but yes, please: fix the darn /opt path first!! libraries should go in /usr/lib/tde (or somesuch), qt3 should go in /usr/lib/qt3 to keep the namespaces totally separate from qt4, qt5, and so on.

l. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-devel. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting

Re: PICCORO's and Luke's comments In general I agree with both of them, but... The improvements and fixes, that they and others want (me too), are beyond the resources that are currently available. As technology improves (or maybe I should say "keeps changing") the problems with TDE will get worse. Continuing to Kludge things, just to get around new software conflicts and other changes--yet still keep TDE working--can only last so long and go so far. I personally want to keep TDE on my computer until I die, and that is looking more difficult everyday. My solution, which I suggest the TDE staff looks into, is using containers, like Docker, to encapsulate TDE with all the software that it needs to function correctly. When you do that, upgrading software outside the container, does not alter what happens inside the container, which cures all of the issues like installing a newer version of GTK or QT trashing TDE. When you use containers, you no longer need to create individual versions or packages of TDE for every Distro. This fall I plan on creating my own TDE container that will sit on top of Devuan. If all works well I will share that TDE container as well as the complete TDE/Devuan setup, with anyone that wants it. Keith On Sat, Jun 17, 2017 at 12:30 PM, PICCORO McKAY Lenz < mckaygerhard(a)gmail.com&gt; wrote:

Keith Daniels wrote: I was thinking of this few days ago, but in different context. As PICCORO McKAY Lenz stated a container is waste of resources, however what you use is your own decision, so perhaps you could setup a build env and try to produce the packages for devuan or what you think might be useful and go for it as proof of concept. I personally use chroot for building packages and vmware to test and I think it is sufficient. Containers are cool, but I don't see advantage in maintaining such overhead. I can of course speak only for myself. At the end I want to have TDE native and not in some kind of virtual env. regards --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-devel. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting