Merge pull request #3005 from robotology/yarp_no_ros

Yarp no-ros

.github/CODEOWNERS

@@ -59,7 +59,6 @@
 /src/libYARP_run/**                              @drdanz
 /src/libYARP_serversql/**                        @drdanz
 /src/libYARP_sig/**                              @drdanz
-/src/libYARP_wire_rep_utils/**                   @drdanz
 /src/portmonitors/depthimage_compression_zfp/**  @Nicogene
 /src/portmonitors/depthimage_to_mono/**          @randaz81
 /src/portmonitors/depthimage_to_rgb/**           @randaz81

doc/001_installation/4_yarp_env_variables.dox

@@ -85,15 +85,6 @@ UDP Carrier configuration
 | `YARP_DGRAM_SND_BUFFER_SIZE`  | This variable controls the size in bytes of the UDP socket sending buffer. | |
 
 
-ROS configuration
-=================
-
-| Environmental variable        | Description | Related documentation page |
-|:-----------------------------:|:-----------:|:--------------------------:|
-| `ROS_MASTER_URI`              | If a ROS1 roscore is present in the network, this variable should contain its URI. If a ROS1 installation is present on the machine, this variable is typically set by ROS configuration scripts. | http://wiki.ros.org/ROS/EnvironmentVariables |
-| `YARP_USE_ROS`                | If this variable is set to something different from an empty string, the `yarpserver` will always be launched with `ROS` support. For example ``YARP_USE_ROS=1 yarpserver` is equivalent to `yarpserver --ros`.    | \ref yarp_with_ros_nameservers |
-
-
 Misc configuration
 ==================
 

doc/040_idl_thrift/0_thrift.dox

@@ -8,6 +8,6 @@ IDLs offers a convenient way to define structures and services and separate inte
 \section idls_list List of IDLs (Interface Description Languages) used in YARP
 
 \li \subpage idl_thrift
-\li \subpage idl_rosmsg
+\li \subpage idl_rosmsg <deprecated>
 
 */

doc/040_idl_thrift/thrift_tutorial_portable.dox

@@ -259,15 +259,4 @@ The Thrift IDL also allows defining modules interfaces, this is explained here:
 \li \ref thrift_tutorial_simple
 \li \ref thrift_tutorial
 
-YARP supports ROS types.
-An alternative method to define portable objects in YARP is to use the ROS
-syntax (i.e. through a .msg file).
-The disadvantage of this approach is that you cannot use native YARP types, but
-the advantage is that your messages will be compatible with ROS and readable
-from a topic. This tutorial shows how you do this:
-
-\li \ref rostypes_tutorial_portable
-
-Code for this tutorial can be found here: `example/idl/portable`
-
 */