[ros-users] [Ros-release] REP for Third Party Package Releasing

William Woodall wwoodall at willowgarage.com
Wed Feb 20 22:57:16 UTC 2013


It is implemented in catkin (support for built_type tag), and it is
implemented in bloom version 0.3, which has been implemented but not
released yet. I have links to the new tutorials and documentation for bloom
in the Resources section of the REP.  I am drafting an annotated version of
bloom's change log as an email to the buildsystem sig, and then we plan to
test it out by (re)blooming things for the Hydro build farm bring up.
Hopefully after that test bloom 0.3 will be released and everything
described here will work as expected.

If you _really_ want to give the new bloom a shot, it is functionally
complete and you can try it from source:

$ git clone https://github.com/ros-infrastructure/bloom
$ cd bloom
$ sudo python setup.py develop

Now that will setup bloom to work from source. When you are done:

$ sudo python setup.py develop -u
$ sudo rm -rf /usr/local/bin/bloom-* /usr/local/bin/git-bloom-*

Unfortunately the distribute develop mode does not remove the place holder
scripts from /usr/local/bin, so that must be done manually.

I have to warn users that mixing this develop mode and the python-bloom
debian can cause problems if they do not follow those directions exactly
when removing it. I would say that unless you know what you are doing you
should wait for the release.

Please continue any feed back either on the ros-sig-buildsystem mailing
list or on the bloom issue tracker.


On Wed, Feb 20, 2013 at 2:40 PM, Ruben Smits
<ruben.smits at intermodalics.eu>wrote:

> Hi William,
> Op woensdag 20 februari 2013 schreef William Woodall (
> wwoodall at willowgarage.com) het volgende:
>  I have drafted a REP, tentatively REP-136, which is an Informational REP
>> providing a recommendation for how to release third party packages into the
>> ROS ecosystem. In this context a third party package is any software
>> package which is used in the ROS ecosystem, but exists outside of the ROS
>> ecosystem, and therefore is neither catkin based nor rosbuild based.
>> You can find this draft REP here:
>> https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst
>> And the pull request containing the drafting history is here:
>> https://github.com/ros-infrastructure/rep/pull/23
>> To summarize the recommendation, third party packages should:
>>    - Have a package.xml
>>       - Which run_depend's on catkin
>>       - Has a <build_type> tag in the <export> section
>>    - Install the package.xml
>> Notice this recommendation does not involve buildtool_depend'ing on
>> catkin, and it does not require the use of catkin in the build system. This
>> can either be accomplished by putting the package.xml and its install rule
>> into the upstream repository of the third party library or by injecting the
>> package.xml and install rule into the release repository using bloom.
> Is the functionality described in the REP already available in catkin and
> bloom? In other words, can we try out the described functionality?
> Ruben
>> The REP covers many more details related to the rationale of this
>> recommendation, consequences of this style of releasing third party
>> packages, and links to resources related to this change.
>> Please submit any feedback to the ros-sig-buildsystem mailing list.
>> Thanks,
>> --
>> William Woodall
>> Willow Garage - Software Engineer
>> wwoodall at willowgarage.com
> --
> Ruben Smits, Phd
> Chief Technology Officer
> Intermodalics BVBA
> +32479511786
> www.intermodalics.eu

William Woodall
Willow Garage - Software Engineer
wwoodall at willowgarage.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20130220/0432b7d5/attachment-0004.html>

More information about the ros-users mailing list