[Rock-dev] [rock] #452: base/orogen/std typekit missing includes for boost/cstdint

[rock]

#452: base/orogen/std typekit missing includes for boost/cstdint
--------------------+---------------------
 Reporter:  jasc02  |       Owner:
     Type:  defect  |      Status:  closed
 Priority:  major   |   Milestone:
Component:  base    |  Resolution:  fixed
 Keywords:          |
--------------------+---------------------

Comment (by sylvain.joyeux):

 Replying to [comment:8 Alexander.Duda]:
 > Replying to [comment:6 sylvain.joyeux]:
 > > Replying to [comment:4 Alexander.Duda]:
 > > > In any case we should probably no longer track rtt master by default
 to avoid such problems.
 > >
 > > I don't agree. What we should not do is *track* master when working
 two weeks before demos. And when I say "not track master", I mean "not
 track ANY master".
 > Agreed, but unfortunately this is not the case for most of the systems.

 Which is what we need to tackle. Pinning RTT won't help with the bigger
 issue, which is that now that 4+ institutes start using Rock, demo
 schedules will vary, agendas will vary and not one team / place / company
 can assume that everyone will follow *their* constraints. Meaning that the
 issue that you had today with RTT, you or somebody else might have it
 tomorrow with PCL, OpenCV, rbind, iodrivers_base, ...

 We need to solve the issue of "everyone feels like they have to work on
 master" once and for all.

 RTT is not a special case here (and, quite honestly, RTT has one of the
 best track records when it comes to not breaking master. It was a very
 trivial fix, and the error was mostly on Rock's side). See MARUM and the
 (unintended) impact of changes in vizkit...

-- 
Ticket URL: <http://rock.opendfki.de/ticket/452#comment:10>
rock <http://rock.opendfki.de>
rock: the robot construction kit