Update to formatting of package manifest REPs (#26)

* Update formatting of REP-0127

Signed-off-by: SuperJappie08 <[email protected]>

* Update formatting of REP-0140

Signed-off-by: SuperJappie08 <[email protected]>

* Update formatting of REP-0149

This is a mostly direct port of the style resulting from the original
source. It does not have work well with dark mode.

Signed-off-by: SuperJappie08 <[email protected]>

---------

Signed-off-by: SuperJappie08 <[email protected]>

Author: SuperJappie08

_posts/rep-0127.md

@@ -128,11 +128,11 @@ All other tags are nested under it.
 
 The required tags in a `package.xml` file provide package meta-data:
 
-> - [\\\<name\\\>]()
-> - [\\\<version\\\>]()
-> - [\\\<description\\\>]()
-> - [\\\<maintainer\\\> (multiple, but at least one)]()
-> - [\\\<license\\\> (multiple, but at least one)]()
+> - [\<name\>](#name)
+> - [\<version\>](#version)
+> - [\<description\>](#description)
+> - [\<maintainer\> (multiple, but at least one)](#maintainer-multiple-but-at-least-one)
+> - [\<license\> (multiple, but at least one)](#license-multiple-but-at-least-one)
 
 ### Optional Tags
 
@@ -141,66 +141,68 @@ The required tags in a `package.xml` file provide package meta-data:
 Optional, but recommended, meta-data include the names of the original
 authors and links to support documentation.
 
-> - [\\\<url\\\> (multiple)]()
-> - [\\\<author\\\> (multiple)]()
+> - [\<url\> (multiple)](#url-multiple)
+> - [\<author\> (multiple)](#author-multiple)
 
 #### Dependencies
 
 The dependencies and relations to other packages and system packages
 have been discussed in[^7] and are described using:
 
-> - [\\\<build_depend\\\> (multiple)]()
-> - [\\\<buildtool_depend\\\> (multiple)]()
-> - [\\\<run_depend\\\> (multiple)]()
-> - [\\\<test_depend\\\> (multiple)]()
-> - [\\\<conflict\\\> (multiple)]()
-> - [\\\<replace\\\> (multiple)]()
+> - [\<build_depend\> (multiple)](#build_depend-multiple)
+> - [\<buildtool_depend\> (multiple)](#buildtool_depend-multiple)
+> - [\<run_depend\> (multiple)](#run_depend-multiple)
+> - [\<test_depend\> (multiple)](#test_depend-multiple)
+> - [\<conflict\> (multiple)](#conflict-multiple)
+> - [\<replace\> (multiple)](#replace-multiple)
 
 #### Various
 
 There is a need for additional meta-data in the manifest for other tools
 that work with packages, like message generators and plugin discovery.
 All of this *dynamic* information is stored in tags under a single tag:
 
-> - [\\\<export\\\>]()
+> - [\<export\>](#export)
 
 Tool providers are responsible for defining the tag structure their tool
 requires.
 
 ### Example
 
-    <package>
-      <name>my_package</name>
-      <version>1.2.3</version>
-      <description>
-        ROS communications-related packages, including core client
-        libraries (roscpp, rospy, roslisp) and graph introspection tools
-        (rostopic, rosnode, rosservice, rosparam).
-      </description>
-      <maintainer email="[email protected]">Someone</maintainer>
+```xml
+<package>
+  <name>my_package</name>
+  <version>1.2.3</version>
+  <description>
+    ROS communications-related packages, including core client
+    libraries (roscpp, rospy, roslisp) and graph introspection tools
+    (rostopic, rosnode, rosservice, rosparam).
+  </description>
+  <maintainer email="[email protected]">Someone</maintainer>
 
-      <license>BSD</license>
-      <license>LGPL</license>
+  <license>BSD</license>
+  <license>LGPL</license>
 
-      <url type="website">http://wiki.ros.org/my_package</url>
-      <url type="bugtracker">http://www.github.com/my_org/my_package/issues</url>
-      <author>John Doe</author>
-      <author email="[email protected]">Jane Doe</author>
+  <url type="website">http://wiki.ros.org/my_package</url>
+  <url type="bugtracker">http://www.github.com/my_org/my_package/issues</url>
+  <author>John Doe</author>
+  <author email="[email protected]">Jane Doe</author>
 
-      <buildtool_depend>catkin</buildtool_depend>
-      <build_depend version_gte="1.1" version_lt="2.0">genmsg</build_depend>
+  <buildtool_depend>catkin</buildtool_depend>
+  <build_depend version_gte="1.1" version_lt="2.0">genmsg</build_depend>
 
-      <build_depend>libgstreamer0.10-dev</build_depend>
-      <run_depend>libgstreamer0.10-0</run_depend>
+  <build_depend>libgstreamer0.10-dev</build_depend>
+  <run_depend>libgstreamer0.10-0</run_depend>
 
-      <test_depend>gtest</test_depend>
+  <test_depend>gtest</test_depend>
 
-      <conflict>my_old_package</conflict>
+  <conflict>my_old_package</conflict>
 
-      <export>
-        ...
-      </export>
-    </package>
+  <export>
+    ...
+  </export>
+</package>
+```
 
 ### \<name\>
 
@@ -247,7 +249,9 @@ they can claim maintainership:
 
 #### Example
 
-    <maintainer email="[email protected]">Unmaintained see http://wiki.ros.org/MaintenanceGuide#Claiming_Maintainership</maintainer>
+```xml
+<maintainer email="[email protected]">Unmaintained see http://wiki.ros.org/MaintenanceGuide#Claiming_Maintainership</maintainer>
+```
 
 ### \<license\> (multiple, but at least one)
 
@@ -351,7 +355,7 @@ system.
 
 #### Attributes
 
-> The same attributes as for [\\\<build_depend\\\> (multiple)]().
+> The same attributes as for [\<build_depend\> (multiple)](#build_depend-multiple).
 
 ### \<run_depend\> (multiple)
 
@@ -371,7 +375,7 @@ are built.
 
 #### Attributes
 
-> The same attributes as for [\\\<build_depend\\\> (multiple)]().
+> The same attributes as for [\<build_depend\> (multiple)](#build_depend-multiple).
 
 ### \<test_depend\> (multiple)
 
@@ -383,7 +387,7 @@ A `<test_depend>` may not reference any package also declared using a
 
 #### Attributes
 
-> The same attributes as for [\\\<build_depend\\\> (multiple)]().
+> The same attributes as for [\<build_depend\> (multiple)](#build_depend-multiple).
 
 ### \<conflict\> (multiple)
 
@@ -396,7 +400,7 @@ and[^10].
 
 #### Attributes
 
-> The same attributes as for [\\\<build_depend\\\> (multiple)]().
+> The same attributes as for [\<build_depend\> (multiple)](#build_depend-multiple).
 
 ### \<replace\> (multiple)
 
@@ -405,7 +409,7 @@ This maps to `Replaces` for `dpkg` and `Obsoletes` for `rpms`.
 
 #### Attributes
 
-> The same attributes as for [\\\<build_depend\\\> (multiple)]().
+> The same attributes as for [\<build_depend\> (multiple)](#build_depend-multiple).
 
 ### \<export\>
 
@@ -418,9 +422,11 @@ Existing rosbuild export tags for tools using `pluginlib` remain
 unchanged. For example, a package which implements an rviz plugin might
 include this:
 
-    <export>
-      <rviz plugin="${prefix}/plugin_description.xml"/>
-    </export>
+```xml
+<export>
+  <rviz plugin="${prefix}/plugin_description.xml"/>
+</export>
+```
 
 The following are some tags used within an `<export>` for various
 package and message generation tasks.
@@ -445,21 +451,25 @@ notify users about that fact. The tag may be empty or may optionally
 contain an arbitrary text providing user more information about the
 deprecation:
 
-    <export>
-      <deprecated>
-        This package will be removed in ROS Hydro. Instead, use package
-        FOO, which provides similar features with a different API.
-      </deprecated>
-    </export>
+```xml
+<export>
+  <deprecated>
+    This package will be removed in ROS Hydro. Instead, use package
+    FOO, which provides similar features with a different API.
+  </deprecated>
+</export>
+```
 
 #### \<message_generator\>
 
 The content defines the *identifier* for the language bindings generated
 by this package, i.e. in `gencpp` this is set to `cpp`:
 
-    <export>
-      <message_generator>cpp</message_generator>
-    </export>
+```xml
+<export>
+  <message_generator>cpp</message_generator>
+</export>
+```
 
 #### \<metapackage/\>
 
@@ -481,24 +491,30 @@ robot and then provide a comprehensive grouping for your whole system.
 Every metapackage must have a `CMakeLists.txt` containing these
 commands:
 
-    cmake_minimum_required(VERSION 2.8.3)
-    project(PACKAGE_NAME)
-    find_package(catkin REQUIRED)
-    catkin_metapackage()
+```cmake
+cmake_minimum_required(VERSION 2.8.3)
+project(PACKAGE_NAME)
+find_package(catkin REQUIRED)
+catkin_metapackage()
+```
 
 Because the metapackage `CMakeLists.txt` contains a catkin macro, its
 `package.xml` must declare a buildtool dependency on catkin:
 
-    <buildtool_depend>catkin</buildtool_depend>
+```xml
+<buildtool_depend>catkin</buildtool_depend>
+```
 
 Additional buildtool, build or test dependencies are not permitted.
 
 Metapackages list all packages or other metapackages in their group
 using `<run_depend>` tags:
 
-    <run_depend>your_custom_msgs</run_depend>
-    <run_depend>your_server_node</run_depend>
-    <run_depend>your_utils</run_depend>
+```xml
+<run_depend>your_custom_msgs</run_depend>
+<run_depend>your_server_node</run_depend>
+<run_depend>your_utils</run_depend>
+```
 
 ## Compatibility