To whom it may concern.
I’ve been able to run up a trytond server from the tryton-server ‘meta’ port with and without a postgresql server, and with and without uWSGI, and activated all trytond package both on an sqlite file-based database as well as on a postgres database. Modules should be current LTS 7.0.x as per today.
Subsequently, I consider the set of ports generally ready for the wild. The tryton-server port installs corresponding config files sufficient for starting up a server and do the first clickabouts if instructions in the overly long pkg-message are followed.
As usual, and in good porting tradition, the good admin will have to adjust to her or his likings and local requirement but I feel I’ve been left in the middle of nowhere too many times that I consider the effort worth the while it took me (along with learning sme myself, of course).
In any case, I hope that someone finds this useful, and maybe some other even be willing to contribute to maintaining the ports bunch. I’ll continue to keep a bit of an eye to it, set up some jail and be done with it for the time being as it was intended as a ‘quick port’ of what is a tool to me at this time (which does not lessen its importance) but which has consumed much more time than I anticipated. I now intend to move towards actually using Tryton… 
When I see module updates on pypi, I intend to add them (unless someone else is faster than me). If I can figure out how to add the web interface to the ports, I eventually may do that, because the tryton client seems to have some funny GUI issues on my box; gunicorn possibly also but it currently has a lesser prio, to be honest, since uWSGI seems to work.
Again, thank you very much indeed to those who responded and gave guidance, here, and via documentation elsewhere, and a big hand to all who developed and develop Tryton.
Likely read you soon, and please be in touch if you think I can be of help.
Cheers,
Peter.
PS. If anyone had investigated how much the new (?) German ‘eRechnung’ requirements (cf. [1], [2] below) would deviate from the ‘French’ UN/CEFACT which we already seem to have in the modules, I’d love to learn eventually (true beginner at this stage, though, sorry).
[1] Pflicht zur E-Rechnung im XML-Format: Das ist der Status quo | heise online
[2] Gemeinsamer Rechnungsstandard: ZUGfeRD und Factur-X | heise online