On Fri, May 12, 2017 at 10:41 PM, Keith Daniels <keithwdaniels@xxxxxxxxx> wrote: > 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. yehyeah, i can attest to that: likewise i ran into problems with a devuan/testing system 18 months (or so) ago, it wouldn't actually install trinity *at all* due to package conflicts. basically this is the usual issue with having separate package repositories that are not compiled often enough: the fact that there are *two* completely separate repositories means that anyone who wants to use devuan/testing - which will be critical moving forward for anyone doing any kind of software development or for anyone who wishes to e.g. use the absolute latest CUPS drivers for example so that their MODERN printers work - is basically SOL. 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@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx 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
