Re: [trinity-devel] Trinity Application Descriptions

That pretty much is how I accumulated my notes about external packages. Those packages are not dependencies, but external icing on the cake. I don't pretend to know what additional functionality each of those hooks provide, I only know that when those external packages are not installed I see related messages during the configure process (now cmake with several packages). I mentioned in a previous response I could provide those notes if requested. I suppose I should just post them. :)