[ros-users] epydoc broken with rosdoc

[Dirk Thomas]

You can just register the git repository.
Than all packages inside that repo will be documented.

If you only want to document parts of your repository you need to separate them.

- Dirk



On 20.05.2013 11:36, Dan Lazewatsky wrote:
> If I have a whole stack in a single git repo, since git doesn't allow partial checkouts, will I have to split each package into its own repo, or is there a way around that for doc.yaml?
>
> On Thu, May 16, 2013 at 3:43 PM, Dirk Thomas <dthomas at osrfoundation.org <mailto:dthomas at osrfoundation.org>> wrote:
>
>     For the new rosdistro format (Groovy and higher) all dependencies must be listed in the doc.yaml file.
>     Only then you can refer to them as a dependency for another repository.
>
>     - Dirk
>
>
>
>
>     On 16.05.2013 12:13, Dan Lazewatsky wrote:
>
>         Thanks, Dirk -
>         "projector_interface" is in a package which is part of a stack which is in doc.yaml. Am I ok to add the depends line, or does "projector_interface" need to be explicitly defined in doc.yaml?
>
>         -Dan
>
>         On Mon, May 13, 2013 at 5:53 PM, Dirk Thomas <dthomas at osrfoundation.org <mailto:dthomas at osrfoundation.org> <mailto:dthomas at osrfoundation.__org <mailto:dthomas at osrfoundation.org>>> wrote:
>
>              Build #13 was failing because GitHub was not reachable at that time.
>              But build #14 is failing because the dependency "projector_interface" is unavailable.
>              If that package ist not released and available as a Debian package you need to add it as a depends.
>              Therefore you have to add the repo containing "projector_interface" to the groovy/doc.yaml file and reference it as a "depends" for the documented repo "projected-interface-builder"
>         (search for
>              "depends" in the doc.yaml file for examples).
>
>              - Dirk
>
>
>
>
>
>         _________________________________________________
>         ros-users mailing list
>         ros-users at code.ros.org <mailto:ros-users at code.ros.org>
>         https://code.ros.org/mailman/__listinfo/ros-users <https://code.ros.org/mailman/listinfo/ros-users>
>
>
>     _________________________________________________
>     ros-users mailing list
>     ros-users at code.ros.org <mailto:ros-users at code.ros.org>
>     https://code.ros.org/mailman/__listinfo/ros-users <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
>