RHEL-based environments README update

README.md

@@ -21,14 +21,16 @@ Below you'll find the installation steps. You can also find a [Troubleshooting g
 
 On Debian/Ubuntu environments, make sure to install these packages: 
 ```
-python python-dev python-virtualenv qt5-default libcurl4-openssl-dev libxml2 libxml2-dev libxslt1-dev libssl-dev virt-viewer
+python3 python3-dev python3-virtualenv qt5-default libcurl4-openssl-dev libxml2 libxml2-dev libxslt1-dev libssl-dev virt-viewer
 ```
 
 On RHEL environments, make sure to install these packages:
 ```
-python python-devel python-virtualenv python-pip gcc gcc-c++ qt5-qtbase qt5-qtbase-devel libcurl-devel libxml2 libxml2-devel libxslt-devel openssl-devel virt-viewer
+python36 python36-devel python36-virtualenv python36-pip gcc gcc-c++ qt5-qtbase qt5-qtbase-devel libcurl-devel libxml2 libxml2-devel libxslt-devel openssl-devel virt-viewer
 ```
 
+**Important for RHEL based environments**: Please note that in further steps, commands may vary in RHEL based environments. For example, it's likely your virtualenv command will be `virtualenv-3.6`, and your pip command will be `pip-3.6`. Please find the correct command in your case.
+
 Now just clone, install a virtualenv with Python3 as the Python executable and install the requirements for the project.
 
 ```
@@ -53,6 +55,8 @@ git pull
 pip install -r requirements.txt
 ```
 
+Check the `settings.conf.example` file just to check if you have all parameters up to date, and add those missing in your `settings.conf` file.
+
 ### Configuration
 
 To run the application, a file named `settings.conf` must exist in the same directory where the application resides. This file contains 2 sections with a few parameters in each. You can find a `settings.conf.example` file inside the repository so you can base your configuration on it (don't forget to copy/rename it to `settings.conf`).

TODOLIST

@@ -1,4 +1,3 @@
-* Migrate oVirt code to 4.X.X version. While ovirt-engine-sdk-python version 3.X.X is compatible with oVirt API 4.0.0, in the future this backwards compatibility will be removed. The oVirt code should all be rewritten to 4.X.X format.
 * Implement the "multitenant" mode (showing machines of multiple instances of oVirt into the same application).
 * Implement an "unexitable" mode (for Kiosk mode).
 * Include an option to make the main window modal.