python3-dev is another dependency of the Python bindings

[simgrid.git] / docs / source / Deploying_your_application.rst

diff --git a/docs/source/Deploying_your_application.rst b/docs/source/Deploying_your_application.rst
index 7064655..4cd1287 100644 (file)
--- a/docs/source/Deploying_your_application.rst
+++ b/docs/source/Deploying_your_application.rst
@@ -19,7 +19,7 @@ There is several ways to deploy the :ref:`application <application>` you want to
 study on your :ref:`simulated platform <platform>`, i.e. to specify which actor
 should be started on which host. You can do so directly in your program (as
 shown in :ref:`these examples <s4u_ex_actors>`), or using an XML deployment
-file. Unless you have a good reason, you should keep your application apart
+file. Either way, it is a good habit to keep your application apart
 from the deployment as it will :ref:`ease your experimental campaign afterward
 <howto_science>`.
 
@@ -76,14 +76,6 @@ This tag starts a new actor executing the given function on a given host.
    with :cpp:func:`simgrid::s4u::Engine::register_actor` or
    with :cpp:func:`simgrid::s4u::Engine::register_function`.
 
-   If you are stuck with MSG, use :cpp:func:`MSG_process_create`,
-   :cpp:func:`MSG_process_create_with_arguments` or
-   :cpp:func:`MSG_process_create_with_environment`.
-
-   There is nothing to do in Java, as SimGrid uses introspection abilities to
-   retrieve the classes from their names. You must then use the full class name
-   (including the package name) in your XML file.
-
 :``start_time``: Useful to delay the start of your actor.
 
         -1 starts the actor immediately.