Hey Jack
I thought of another thing.
My understanding is that the popen/system call was used in beadm to
invoke an ICT written in C. A C to Python bridge was in the planning
for the ICT's written in Python but it was never done. Perhaps it
might be better to do some of that now. Maybe just provided the C->py
bridge for the ICT(s) used by beadm for now. Other bridges can be
added as needed.
What do you think about this approach?
Not sure I understand your point. From your comment:
Currently:
beadm(python) -> libbe(C) -> system() -> ICT(C)
Planning:
beadm(python) -> libbe(C) -> ICT(python)
Are you suggesting that I write a C->python bridge for ICTs and convert
the add_splash_image_to_grub_menu ICT to python?
Doing that work would be out of scope from what I am doing for SNAP->ON
integration. Or do I misunderstand?
In scope is to make sure that the current ICT gets called properly and
any errors it returns get propagated back to the screen via beadm's
error handling.
Thanks,
Jack
Joe
Hey Jack,
Thanks for the reply.
add_splash_image_to_grub_menu ICT is already implemented in Python in:
<slim_source>/usr/src/lib/libict_pymod/ict.py
There is no C->python bridge for ICTs. However the Python ICT's were
developed with an interface which can be invoked from the shell. This
was done mostly for testing but could also be used until the bridges
where developed.
libbe had been leveraging that interface through system(3c).
Currently:
beadm(python) -> libbe(C) -> system() -> shell -> ICT("python")
What I am proposing is adding "C_python_bridge_for_ICT":
beadm(python) -> libbe(C) -> C_python_bridge_for_ICT -> ICT(python)
Let's talk this over. I'll try to call.
Joe
Hi Joe.
Thanks for the clarification about the ICT being written in python already.
While writing a C->Python bridge may be helpful, I don't see how it
gives a return large enough to warrant doing it at this time. Glenn and
I are under a tight deadline to finish, and as I said earlier, it would
extend the scope of my work.
Thanks,
Jack
P.S. I tried calling you as well.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
