[ros-users] stereo in diamondback release

[Ken Conley]

On Wed, Feb 9, 2011 at 9:07 AM, Asghari Oskoei, Mohammadreza
<m.asghari-oskoei at herts.ac.uk> wrote:
>
> joq
> thank you for the reply,
> so can we say regularly "unstable" is fresher than the "diamondback", and we can get required packages by "sudo apt-get install ros-unstable-XXXX"?

This statement isn't strictly true.  When we were releasing cturtle,
for example, cturtle was actually fresher (newer) than unstable.  For
diamondback, we are using unstable to buffer and test releases for
diamondback, so in this case, it is fresher.

Similarly, if a new feature is being developed on unstable, it may
actually take longer to deploy a bug fix than on diamondback.

 - Ken

>
> Reza,
>
>
>
> -----Original Message-----
> From: ros-users-bounces at code.ros.org [mailto:ros-users-bounces at code.ros.org] On Behalf Of Jack O'Quin
> Sent: 09 February 2011 16:51
> To: User discussions
> Subject: Re: [ros-users] stereo in diamondback release
>
> On Wed, Feb 9, 2011 at 10:22 AM, Asghari Oskoei, Mohammadreza
> <m.asghari-oskoei at herts.ac.uk> wrote:
>>
>> I wonder to being able to have new releases developed for stereo image sync
>> (--approximate=0.01 in python script and _approximate_sync:=True in cpp) we
>> can use just pre-compiled diamondback (sudo apt-get ...) or should download
>> and compile SVN sources. I basically prefer to use the pre-compiled release,
>> but in a download that I did a few days ago, the above mentioned arguments
>> were not working, so used the source.
>>
>> What a time gap is in-between uploaded pre-compiled and source releases?
>
> It varies. My impression is that binary debs are usually available
> within a week after the source release.
>
>> What does "unstable" mean? WG-specific installation?
>
> It means packages under development for the next distribution. Not
> necessarily WG.
>
> Unstable was used to develop packages for diamondback. Now that
> diamondback beta is out, they are (roughly) the same. Once the final
> diamondback distribution is released, unstable will begin development
> for the next distribution (E-turtle).
>
>> How can we get sure that we have got the latest diamondback and all related
>> packages such as PR2, cob, ...
>
> New deb binaries will be released as available. You should get them
> automatically via System>Administration>Update Manager or "sudo
> apt-get upgrade".
>
>> What do you recommend about packages that we had in cturtle but can't find
>> in diamondback, such as camera_drivers (prosilica_camera node), should we
>> copy them from cturtle?
>
> No. The cturtle packages are not compatible. There have been binary
> interface changes.
>
> For diamondback, the packaging became less monolithic. People are not
> expected to download almost everything. REP 108 explains the new
> scheme:
>
>  http://www.ros.org/reps/rep-0108.html
>
> Different variants comprise various subsets of the packages. I see
> there is a care-o-bot variant, so you should get most of what you need
> by installing ros-diamondback-care-o-bot.
>
> Since that does not appear to include ros-diamondback-camera-drivers,
> you may need to install that separately. If most or all care-o-bot
> users need the camera_drivers, someone should probably add it to the
> care-o-bot variant.
> --
>  joq
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>