hi ken,
There are ros packages, openrave in my case, that are independent of
the ros version. It would be difficult to manage two copies of this
package for every copy of the openrave_planning stack there is....
Also, it would be simpler for me to support old ros versions by
#ifdef'ing stuff that changes rather than support two working copies.
Of course, once we do feel confident enough for official releases, we
would just have one working copy (against the current stable ros
release) and make releases of this stack for each different ros
version.
What would you recommend in this case? Please advise
thank you,
rosen,
2010/8/4 Ken Conley <
kwc@willowgarage.com>:
> Hi Dejan,
>
> My e-mail only pertains to unreleased code inside of two URLs:
>
> https://code.ros.org/svn/wg-ros-pkg/trunk/
> https://code.ros.org/svn/ros-pkg/trunk/
>
> These are generally the "sandbox" packages.
>
> motion_planning_visualization (and all other released stacks) remain
> unchanged.
>
> We did this for unreleased code because we previously had not been managing
> the versions of these unreleased packages. This meant, for example, that we
> could not run our build system against trunk reliably. Unreleased code will
> always be unstable and volatile by its very nature.
>
> - Ken
>
> On Wed, Aug 4, 2010 at 3:09 PM, Dejan Pangercic <dejan.pangercic@gmail.com>
> wrote:
>>
>> Hi Ken,
>>
>> I am updating my installation and I just noticed that the
>> "mapping_rviz_plugin" package did not get moved to
>> "branches/trunk_cturtle"
>>
>> (https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_visualization/trunk/mapping_rviz_plugin).
>> How come this?
>>
>> Last but no least I got a feeling that install/check out urls and
>> routines have been changing very, very frequently. This at least my
>> case creates quite some confusion. I do not know how other feel about
>> it!?
>>
>> D.
>>
>> On Wed, Aug 4, 2010 at 1:31 AM, Ken Conley <kwc@willowgarage.com> wrote:
>> > We've moved the contents of wg-ros-pkg/trunk and ros-pkg/trunk to
>> > separate 'trunk_cturtle' branches. Now that C Turtle is out, we are
>> > maintaining code against multiple distributions (Box Turtle, C Turtle,
>> > and Unstable). It has become necessary for us to start maintaining
>> > better version and API consistency for our code. We also feel that
>> > this is a good time to make this transition as most of our code has
>> > been transitioned to stacks that you can install separately. The code
>> > that remains in our trunks is generally very unstable and should be
>> > avoided by most users.
>> >
>> > If you are using packages from this location, you'll find them moved
>> > here:
>> >
>> > https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/
>> > https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/
>> >
>> > As the URL suggests, these packages will be developed against C Turtle
>> > libraries and remain consistent with those APIs. Packages that are
>> > developed for Diamondback Turtle will be located in wg-ros-pkg/trunk
>> > and ros-pkg/trunk.
>> >
>> > -- your friendly neighborhood Repo man
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users@code.ros.org
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>>
>>
>>
>> --
>> MSc. Dejan Pangercic
>> PhD Student/Researcher
>> Intelligent Autonomous Systems Group
>> Technische Universität München
>> Telephone: +49 (89) 289-26908
>> E-Mail: dejan.pangercic@cs.tum.edu
>> WWW: http://ias.cs.tum.edu/people/pangercic
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
(text/plain)