    == Upgrading from a previous version ==
If you had an earlier version of RutilT, you may be concerned about those
warnings :
    - Before v0.16, profiles were recorded in one file (or several eventually)
for each interface. This is no longer the case, as a result, profiles recorded
with earlier versions will not be loaded.
    - Starting from v0.16, RutilT's data directory is now (by default)
/usr/local/share/apps/rutilt, it was /usr/local/share/rutilt/ prior to this
version.
    - The location where RutilT's icons are installed has changed between v0.15
and v0.16, it used to be (by default) /usr/local/share/pixmaps/rutilt/, it is
now /usr/local/share/icons/hicolor/<icon_size>/apps/ in accordance with the
freedesktop.org specification ; These files have been renamed accordingly too.
Arts used for the tray icon are not concerned by this change, however, they are
now installed in RutilT's data directory.
    - Up to v0.15 (included), the helper was installed with the various scripts
in $prefix/share/rutilt. Since v0.16, it is installed in $prefix/bin like the
main binary.
    - RutilT v0.15 WPA support for rt2570 is not compatible with older version
of the driver, make sure your rt2570 driver supports WPA2PSK (even if you do
not plan to use it).
    - RutilT's arts are not installed at the same place since v0.14, it was
(by default) /usr/local/share/rutilt/, it is now (by default)
/usr/local/share/pixmaps/rutilt/. You can safely remove previous icons.
    - RutilT's desktop launcher used to be installed in /usr/share/applications
before v0.14. Since that version, the default directory is now
/usr/local/share/applications.
    - RutilT helper's install path has changed between v0.07 and v0.08. Before,
it was /usr/libexec/, it is now /usr/local/share/rutilt/. Ditto with the main
binary, is was previously installed in /usr/bin/, it is now in /usr/local/bin/.
Make sure you erase the old binaries.
    - Rfmontx support was enabled by default in v0.07, this is not the case
in v0.08 anymore.
    - RutilT user's directory has changed between v0.05 and v0.06. Before,
it was $HOME/.rutilt, it is now $HOME/.config/rutilt. Erase your old
directories.
Moreover, the profiles file has been renamed too, the old file will not be
loaded.
    - "make install" installed the program in /usr/sbin before v0.06, it is
now /usr/bin. Make sure you erase your old binary.
    - I made an incompatible change between version 0.03 and 0.04,
erase your "profiles.xml" file if you have created profiles with RutilT v0.03.


    == Requirement ==
To compile RutilT, you need your Linux kernel headers or sources (with wireless
extensions version 16 minimum) and the gtk+2 development files (at least version
2.6). If you have trouble compiling, running or install it, please contact me
(see the README file).


    == Installation ==
First, run "./configure.sh". This script checks if dependencies are fulfilled
and generates some required files and scripts. Check the options with
"./configure.sh --help", or have a look at the section "Compilation options" if
the default settings does not suit you.
NOTE : **Ubuntu** users and people using a distribution where the root account
is disabled, run : "./configure.sh --launcher=external"

Type "make" to compile the program. It is known to compile with g++-3.3,
previous version have not been tested and are unsupported.

Then install RutilT with "make install", it must be done as root if you want to
use the built-in helper launcher and/or install it system-wide.

Finally, run the program with "rutilt".

"make uninstall" (as root if you installed it as root) removes the program.
Note : User's configuration files are kept, they are located in
$USER_HOME/.config/rutilt/ in case you want to remove them too.


    == Compilation options ==
- Run "make clean" to erase all compiled binary.

- To cross-compile RutilT for another kernel, or if your sources are not
installed in the default directory (/lib/modules/`uname -r`/build/), use
the "--kernel_sources=PATH" option, where PATH is your custom path.

- If your kernel sources are not available, and the installed kernel headers
does not match your running kernel, you can force the use of those headers with
the "--force" option. Depending on the wireless extensions version of the
headers and your kernel, this may not be a problem at all.

- To change the default installation path (/usr/local), run the configure.sh
script with the "--prefix=PATH" option, where PATH is your custom path.

- You can change the helper launcher with the "--launcher=built-in | disabled |
nopasswd | external" configure.sh option :
        built-in : Use the built-in launcher, it implies that the helper will
                   be installed setuid (that is the default).
        disabled : No helper, RutilT itself will have to be launched directly
                   as root to change wireless settings.
        nopasswd : Exactly as "built-in", but will not prompt for the root
                   password. Everyone can configure the device like root.
        external : configure.sh will generate a script that will be run
                   when root privileges are needed. This script must launch
                   the helper as root, by default, gksu or kdesu are used but
                   you can freely tune the script to match your need. In that
                   case the helper is not installed setuid.

- To compile RutilT with debugging output enabled, use the "--debug" option.
This turns optimizations off, unless you set your own compilation parameters.

- To specify the compilation parameters, use the "--cflags=YOUR_PARAMETERS"
option.

- You can set the version label with this option : "--version=LABEL_HERE".

Of course, all these options can be combined.
