-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List meta dependencies in meta packages #114
Open
rkent
wants to merge
4
commits into
ros-infrastructure:main
Choose a base branch
from
rkent:meta-dependencies
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f51eba7
Show dependencies in meta packages
rkent c3d5a7f
Update default base-url to <rolling> from obsolete <latest>
rkent 51d2faf
Meta packages have no subdirectories except doc
rkent 2f5485f
Add show_exec_dep to rosdoc2.yaml, avoid 'meta' name
rkent File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
<?xml version="1.0"?> | ||
<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> | ||
<package format="3"> | ||
<name>do_show_dep</name> | ||
<version>0.1.2</version> | ||
<description>forcing show of exec dependencies</description> | ||
<maintainer email="[email protected]">Some One</maintainer> | ||
<license>Apache License 2.0</license> | ||
<depend>basic_cpp</depend> | ||
<exec_depend>full_package</exec_depend> | ||
<exec_depend>minimum_package</exec_depend> | ||
<exec_depend>only_messages</exec_depend> | ||
<exec_depend>only_python</exec_depend> | ||
<export> | ||
<rosdoc2>rosdoc2.yaml</rosdoc2> | ||
</export> | ||
</package> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
## Default configuration, generated by rosdoc2. | ||
|
||
## This 'attic section' self-documents this file's type and version. | ||
type: 'rosdoc2 config' | ||
version: 1 | ||
|
||
--- | ||
|
||
settings: | ||
## If this is true, a standard index page is generated in the output directory. | ||
## It uses the package information from the 'package.xml' to show details | ||
## about the package, creates a table of contents for the various builders | ||
## that were run, and may contain links to things like build farm jobs for | ||
## this package or links to other versions of this package. | ||
|
||
## If false, you can still include content that would have been in the index | ||
## into one of your '.rst' files from your Sphinx project, using the | ||
## '.. include::' directive in Sphinx. | ||
## For example, you could include it in a custom 'index.rst' so you can have | ||
## the standard information followed by custom content. | ||
|
||
## TODO(wjwwood): provide a concrete example of this (relative path?) | ||
|
||
## If this is not specified explicitly, it defaults to 'true'. | ||
generate_package_index: true | ||
|
||
## This setting, if true, attempts to run `doxygen` and the `breathe`/`exhale` | ||
## extensions to `sphinx` regardless of build type. This is most useful if the | ||
## user would like to generate C/C++ API documentation for a package that is not | ||
## of the `ament_cmake/cmake` build type. | ||
always_run_doxygen: false | ||
|
||
## This setting, if true, attempts to run `sphinx-apidoc` regardless of build | ||
## type. This is most useful if the user would like to generate Python API | ||
## documentation for a package that is not of the `ament_python` build type. | ||
always_run_sphinx_apidoc: false | ||
|
||
# This setting, if provided, will override the build_type of this package | ||
# for documentation purposes only. If not provided, documentation will be | ||
# generated assuming the build_type in package.xml. | ||
# override_build_type: 'ament_python' | ||
|
||
# This boolean setting, if provided, determines whether the external dependencies of a package | ||
# are shown in the home page of the documentation, which is useful for packages that are only | ||
# used to force loading of other packages (which are sometimes called meta packages). | ||
# If not set, then the decision to show the external dependencies is made on the following | ||
# heuristics: show if the package has no build_depend, does have exec_depend, and has no | ||
# subdirectories except an optional doc/ subdirectory. | ||
show_exec_dep: true | ||
builders: | ||
## Each stanza represents a separate build step, performed by a specific 'builder'. | ||
## The key of each stanza is the builder to use; this must be one of the | ||
## available builders. | ||
## The value of each stanza is a dictionary of settings for the builder that | ||
## outputs to that directory. | ||
## Required keys in the settings dictionary are: | ||
## * 'output_dir' - determines output subdirectory for builder instance | ||
## relative to --output-directory | ||
## * 'name' - used when referencing the built docs from the index. | ||
|
||
- doxygen: { | ||
name: 'forcing show of exec dependecies', | ||
output_dir: 'generated/doxygen' | ||
} | ||
- sphinx: { | ||
name: 'do_show_dep', | ||
## This path is relative to output staging. | ||
doxygen_xml_directory: 'generated/doxygen/xml', | ||
output_dir: '' | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
<?xml version="1.0"?> | ||
<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> | ||
<package format="3"> | ||
<name>dont_show_dep</name> | ||
<version>0.1.2</version> | ||
<description>explicitly not showing dependencies</description> | ||
<maintainer email="[email protected]">Some One</maintainer> | ||
<license>Apache License 2.0</license> | ||
<exec_depend>basic_cpp</exec_depend> | ||
<exec_depend>full_package</exec_depend> | ||
<exec_depend>minimum_package</exec_depend> | ||
<exec_depend>only_messages</exec_depend> | ||
<exec_depend>only_python</exec_depend> | ||
<export> | ||
<rosdoc2>rosdoc2.yaml</rosdoc2> | ||
</export> | ||
</package> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
## Default configuration, generated by rosdoc2. | ||
|
||
## This 'attic section' self-documents this file's type and version. | ||
type: 'rosdoc2 config' | ||
version: 1 | ||
|
||
--- | ||
|
||
settings: | ||
## If this is true, a standard index page is generated in the output directory. | ||
## It uses the package information from the 'package.xml' to show details | ||
## about the package, creates a table of contents for the various builders | ||
## that were run, and may contain links to things like build farm jobs for | ||
## this package or links to other versions of this package. | ||
|
||
## If false, you can still include content that would have been in the index | ||
## into one of your '.rst' files from your Sphinx project, using the | ||
## '.. include::' directive in Sphinx. | ||
## For example, you could include it in a custom 'index.rst' so you can have | ||
## the standard information followed by custom content. | ||
|
||
## TODO(wjwwood): provide a concrete example of this (relative path?) | ||
|
||
## If this is not specified explicitly, it defaults to 'true'. | ||
generate_package_index: true | ||
|
||
## This setting, if true, attempts to run `doxygen` and the `breathe`/`exhale` | ||
## extensions to `sphinx` regardless of build type. This is most useful if the | ||
## user would like to generate C/C++ API documentation for a package that is not | ||
## of the `ament_cmake/cmake` build type. | ||
always_run_doxygen: false | ||
|
||
## This setting, if true, attempts to run `sphinx-apidoc` regardless of build | ||
## type. This is most useful if the user would like to generate Python API | ||
## documentation for a package that is not of the `ament_python` build type. | ||
always_run_sphinx_apidoc: false | ||
|
||
# This setting, if provided, will override the build_type of this package | ||
# for documentation purposes only. If not provided, documentation will be | ||
# generated assuming the build_type in package.xml. | ||
# override_build_type: 'ament_python' | ||
|
||
# This boolean setting, if provided, determines whether the external dependencies of a package | ||
# are shown in the home page of the documentation, which is useful for packages that are only | ||
# used to force loading of other packages (which are sometimes called meta packages). | ||
# If not set, then the decision to show the external dependencies is made on the following | ||
# heuristics: show if the package has no build_depend, does have exec_depend, and has no | ||
# subdirectories except an optional doc/ subdirectory. | ||
show_exec_dep: false | ||
builders: | ||
## Each stanza represents a separate build step, performed by a specific 'builder'. | ||
## The key of each stanza is the builder to use; this must be one of the | ||
## available builders. | ||
## The value of each stanza is a dictionary of settings for the builder that | ||
## outputs to that directory. | ||
## Required keys in the settings dictionary are: | ||
## * 'output_dir' - determines output subdirectory for builder instance | ||
## relative to --output-directory | ||
## * 'name' - used when referencing the built docs from the index. | ||
|
||
- doxygen: { | ||
name: 'explicitly not showing dependencies', | ||
output_dir: 'generated/doxygen' | ||
} | ||
- sphinx: { | ||
name: 'dont_show_dep', | ||
## This path is relative to output staging. | ||
doxygen_xml_directory: 'generated/doxygen/xml', | ||
output_dir: '' | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
<?xml version="1.0"?> | ||
<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> | ||
<package format="3"> | ||
<name>meta_package</name> | ||
<version>0.1.2</version> | ||
<description>Meta package</description> | ||
<maintainer email="[email protected]">Some One</maintainer> | ||
<license>Apache License 2.0</license> | ||
<exec_depend>basic_cpp</exec_depend> | ||
<exec_depend>full_package</exec_depend> | ||
<exec_depend>minimum_package</exec_depend> | ||
<exec_depend>only_messages</exec_depend> | ||
<exec_depend>only_python</exec_depend> | ||
</package> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Injecting the
base_url
here means that the inter package content jumps out of the local tree of a local build tree, or a mirror etc. I think everything else generally uses relative paths and thus is easily testable in the local location and relocatable. Overall using base_url makes sense, but maybe having the default be "." such that everything is relative. Otherwise we really need to flesh out the documentation and deployment stories. It's a challenge to have to test all the docs at one URL or file path. But then have to rebuild them to deploy. Before this the only locations using the base_url are the doxygen tags and sphinx inventory files which actually might be helpful for leveraging cross referencing. But also might have issues if we get to supporting them locally for cross referncing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I'll modify this according to your comments, but it might take a few days because this is a busy week for me.