Hello all

Once upon a time, a few years ago, I had the idea of having a "base"
version of orocos.rb without the "magic" stuff that makes the library hard
to maintain, and was designed to make scripting "easier". The objective was
to have a thinner, well-defined base for Syskit without the historical
stuff. The planned name was 'runkit'.

As all "let's do a major migration", it never happened. The result is that
orocos.rb and syskit are now being developed on branches (called
transition-to-runkit) because I never had the time to start the process of
mainlining that stuff.

Anyways

The changes on orocos.rb itself are rather minimal, but I'm seeing
Christoph having problems that have probably been fixed on them. I would
strongly suggest that you take the time to evaluate whether the branches
"work for you" rather first.

Syskit: I'm really not sure whether anyone at DFKI (or somewhere else on
this email list ...) depends on Syskit. I would appreciate having some
inputs about that. There are a LOT more changes there. Mostly bugfixes and
new functionality related to robustness, but even though we're always
trying to keep backward compatibility, it's hard for us to guarantee that
noone was depending on a bug we've closed ;-)

I'm throwing this on this forum to avoid having people duplicate effort
(wink wink Christoph) and see what would be the best option from your
perspective to move all that stuff to master.
-- 



<https://www.tidewise.io/>

<https://www.linkedin.com/company/tidewise>

<https://www.youtube.com/channel/UCqkA0F52ImGGVNORHx770Vg>

Sylvain Joyeux

CTO


+55 21 3923 5048



Rua Santo Cristo, 70 | Santo Cristo

Rio de Janeiro / RJ,  Brasil
_______________________________________________
Rock-dev mailing list
[email protected]
https://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev

Reply via email to