-------- In message <caj6zyqxtczo7gs0_o7iehr2gyoj58xkheoapxw1zsro68hf...@mail.gmail.com> , Guillaume Quintard writes:
>I'm going to vote for "that freeBSD port is absolutely bonkers and probably >deserves the behind-the-barn treatment", specially considering the debian >dependency graph: https://ibb.co/YdXMHRZ The FreeBSD graph is a fully recursive "all dependencies" graph, both for building and running, the debian graph seems to be truncated somehow, because otherwise that would be a very handicapped py3 instance. And as I said: meson is probably not to blame, I just wanted to illustrate my concern. >I'm not fully against rolling out our own system, but for the love of all >that is holy, let's not base it on Make. If all you use make(1) for is running processes, it's as good as anything (except maybe jam(1)). The hard part about make(1) is getting _all_ your dependencies recorded _correctly_ in the makefile. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
