Re: rFSM catkinization

>
> > I'm not very enthusiastic about this patch, IMNSHO it's plain wrong that
> > a generic software library needs to be changed for use in a specific
> > framework.
>
> I fully agree! This is an unmaintainable path...
>
It is obviously unmaintainable as the orocos packages already migrated into
rosbuild, then from rosbuild to catkin for the sake of ROS compatibility.
But it seems that spending time on build systems is fun [/sarcasm]

Sylvain


2014-02-14 9:39 GMT+01:00 Herman Bruyninckx <
[email protected]>:

> On Fri, 14 Feb 2014, Markus Klotzbuecher wrote:
>
> > Hi Ruben,
> >
> > On Do, Feb 13, 2014 at 04:28:47 +0100, Ruben Smits wrote:
> >
> >> we've cleanup our fork to remove the ugly guard changes we did. But we
> >> did do a catkinization of rFSM. It just adds functionality, we do not
> >> break any old use-cases. It just makes it possible now to include rFSM
> >> in a catkin workspace and have all the LUA paths set up automatically.
> >
> > I'm not very enthusiastic about this patch, IMNSHO it's plain wrong that
> > a generic software library needs to be changed for use in a specific
> > framework.
>
> I fully agree! This is an unmaintainable path...
>
> >> Using this patch we can also seamlessly release rFSM into the ROS
> >> ecosystem. (apt-get install ros-hydro-rFSM)
> >>
> >> pull request is available here: https://github.com/kmarkus/rFSM/pull/4
> >
> > I've merged it, since it seems to make your and other users life
> > easier. But I think the long term goal should be to have a generic
> > non-ros debian package.
> >
> > Markus
>
> Herman
> --
> Orocos-Dev mailing list
> [email protected]
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev