The issue with the code (IIRC) is that it requires cmake to compile, for no obvious reason, and cmake is hard to get working, so e.g. building it on MacOS X is a major porting task. And it depends on libraries that I don't have. And there's no layering of the configuration system aspect of the architecture—it just goes and bashes on interfaces and stuff (this is my recollection—I haven't looked at it in a year or so).
These are not bad things that Markus did. Markus was doing what he needed to do to get it running on OpenWRT. But these are real issues, which are preventing me from using the code. For someone who is not an HNCP expert to hack on the code is difficult, and would require substantial work. I could do it, but I have other things I'm working on. If the code were more modular, I could experiment with it. This is the problem I was trying to express. On Fri, Nov 9, 2018 at 6:57 AM Juliusz Chroboczek <[email protected]> wrote: > > Markus, I tried to be really clear about what I was communicating on the > > slide about implementations, but probably failed. > > Indeed. > > A number of your comments about Markus' code were entirely unnecessary. > > -- Juliusz >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
