FreeBSD, make depends on files installed in /usr/ports/x11/trinity #156

Solution:
Copy the git-clone to the specific location /usr/port/x11/trinity

Since TDE is not part of the standard FreeBSD ports tree, it seemed like a more viable way to concentrate everything in the tree in one subfolder. At the same time, it was necessary to use some fixed root of the tree due to the dependencies of individual ports on each other. That's why we used this way.

In addition to the solution using the copy you used, it is possible, for example, to create a symlink.

As of current I am unable , cannot use, the freebsd parallel building tools,poudiere or synth to build x11/trinity.
It is not considered as a "real" freebsd port.
Currently in the process of compiling with make ... the compilation time is serious.
If i just could compile the dependencies parallel over my cpu-cores :)

My experience with FreeBSD is still quite small and therefore I welcome when someone more experienced can add a hand to the work. Regarding poudiere and synth, so far I have only found basic information, because I would like to use such a tool. Synth seems to me easier to use.

We can adjust the structure so that instead of one central directory can be properly integrated into the ports tree. To do this, it probably would be appropriate to create a script to automate synchronization from our git tree in tde-packaging into the ports tree. What do you think about it?

Are there any meta-ports used in FreeBSD to provide a single port to install a complete set of TDE ports?

You can look at #214, where there is a mechanism for incorporating the ports from the git clone tree into the categories in /usr/ports. Therefore, TDE ports should now be smoothly integrated into the system. This should allow the use of system tools to build packages.

In today's update there is a new meta-port x11/tde-meta, which can serve to build all TDE ports. This has set the dependence on the ports placed in the standard structure /usr/ports.

The ports have been updated for the upcoming R14.1.0 and there is prepared integration into the standard port structure in /usr/ports. Therefore, we consider this issue solved. Do not hesitate to reopen issue if necessary.