Yes, if we will add support for remote shell lib, then we should separate local and remote lib.
I include our BDFLs :) @nico and @steven. What are your thoughts on this?
Not sure I like the double underscore prefix. Makes it look like a type which it is not.
I don't think there's enough of them to split them into different files. IMHO just have one lib.sh
I think I'm -1 on having a remote lib. Don't see the point/use case. The generated code should be as simple/stupid as possible. All heavy lifting should be done in the gencode-* scripts. If you think…
While I see the potential value of such a lib.sh library, aren't we in the progress of moving types to python? Are we feeding a dead animal by starting this lib.sh now?
@steven The reason for having a remove lib is for explorers.
While the gencode-* scripts usually do one specific job, they need information from explorers.
Some pieces of information are needed by…
Moving types to Python?
Does this mean that in the future Python will be required to be installed on all target hosts?
No. Target hosts requirements will always stay minimal.
We (Darko) has been experimenting rewriting some of the types in Python. In the last release the __file type is coded in python.
Ah, then I'm relieved. The main reason for me to use cdist is that I can use it to configure devices which will never be capable of running Python.
So eventually manifests and gencode-* scripts can…
@ssrq Regarding python types, you can look at https://code.ungleich.ch/ungleich-public/cdist/tree/beta branch, and beta docs, https://www.cdi.st/manual/beta/cdist-type.html#python-types.
@steven @ssrq Regarding lib, I am still not sure, to have lib, or not to have lib.
I agree that remote code (explorers and code-remote) should be flat, where most, if not all, the logic is done by…
I believe shell types won't be removed from cdist, so people will continue writing types in shell.
Regarding the copying library functions to the remote host, this could be circumvented by implementing a simple preprocessor à la cpp.
@lubo This is because cdist uses generated version file. After cloning and before runningo python setup.py install one should create version file with `make…
Well, if you wanna do it yourself, do something like this (but with setuptools, I don't have a more up-to-date article…