Hi Nick,

One thing you could look at is pulling examples into a higher level package
that provides examples for multiple packages. People looking for demos are
just looking for a template to copy out into their own tree.  We definitely
have had our own issues with package growth due to trying to precisely
manage dependencies; this is a compromise that maintains the minimal
dependencies of the base libraries, while still enabling you to provide
example code.

Hope this helps,
Ken


On Mon, Jun 14, 2010 at 8:06 AM, Dominick Vanthienen <
dominick.vanthienen@mech.kuleuven.be> wrote:

>
>
>
> Dear fellow ROS-users,
>
> I would like to make a package with some functional C class and examples of
> components/nodes that use that functionality.
> An example can be found on:
> http://svn.mech.kuleuven.be/repos/orocos/trunk/kul-ros-pkg/SSC32/
> The files in the src/ directory contain the functionality and
> orocosSSC32Example/ directory contains an example Orocos component which
> uses this functionality.
> In this example the second directory is also a package (nested packages)=>
> you'll have to add it to your $ROS_PACKAGE_PATH seperatly in order to get
> this working.
> Alternative could be:
> *a seperate package next to the package with the functionality, but this
> will lead to a huge number of packages: (one for the C functionallity, one
> for a rosnode example, one for an orocos component example...)
> *everything in one package: but then people need to install Orocos (RTT,
> because it will be in the manifest) for functionality that's not Orocos
> specific (then it has no use of making first a C class...)
> *...
>
> What solution would be most appropriate?
>
> Thanx for your comments
>
> Nick
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>