|
|
@ -8,14 +8,14 @@ by Simon Edwards <simon@simonzone.com>, Sebastian Kügler <sebas@vizzzion.org>
|
|
|
|
|
|
|
|
|
|
|
|
Introduction
|
|
|
|
Introduction
|
|
|
|
------------
|
|
|
|
------------
|
|
|
|
Guidance is a collection of system administration tools for Linux/KDE systems
|
|
|
|
Guidance is a collection of system administration tools for Linux/TDE systems
|
|
|
|
that is designed to be:
|
|
|
|
that is designed to be:
|
|
|
|
|
|
|
|
|
|
|
|
* Update to date
|
|
|
|
* Update to date
|
|
|
|
* High quality, designed with user friendliness as high priority. (That is
|
|
|
|
* High quality, designed with user friendliness as high priority. (That is
|
|
|
|
to say that the tools should get the job done quickly, accurately and with
|
|
|
|
to say that the tools should get the job done quickly, accurately and with
|
|
|
|
as little effort as possible.)
|
|
|
|
as little effort as possible.)
|
|
|
|
* Use KDE and "fit in" with KDE.
|
|
|
|
* Use TDE and "fit in" with TDE.
|
|
|
|
* Maintainable.
|
|
|
|
* Maintainable.
|
|
|
|
* Free Software
|
|
|
|
* Free Software
|
|
|
|
|
|
|
|
|
|
|
@ -63,7 +63,7 @@ Requirements
|
|
|
|
not then it will most definately be available for you distribution of choice.
|
|
|
|
not then it will most definately be available for you distribution of choice.
|
|
|
|
|
|
|
|
|
|
|
|
* PyQt / PyKDE. Version 3.7 or higher. PyQt and PyKDE are distributed with
|
|
|
|
* PyQt / PyKDE. Version 3.7 or higher. PyQt and PyKDE are distributed with
|
|
|
|
KDE as part of kde-bindings since version 3.3.
|
|
|
|
TDE as part of kde-bindings since version 3.3.
|
|
|
|
|
|
|
|
|
|
|
|
For versions of KDE before 3.3 it is possible to install PyQt/PyKDE
|
|
|
|
For versions of KDE before 3.3 it is possible to install PyQt/PyKDE
|
|
|
|
directly. The homepage for PyQt and PyKDE is:
|
|
|
|
directly. The homepage for PyQt and PyKDE is:
|
|
|
@ -80,13 +80,13 @@ Requirements
|
|
|
|
http://www.simonzone.com/software/pytdeextensions/
|
|
|
|
http://www.simonzone.com/software/pytdeextensions/
|
|
|
|
This is also a runtime requirement!
|
|
|
|
This is also a runtime requirement!
|
|
|
|
|
|
|
|
|
|
|
|
* libpythonize. If you don't want the tools to appear on the KDE Control
|
|
|
|
* libpythonize. If you don't want the tools to appear on the TDE Control
|
|
|
|
Center of you just don't want to bother with libpythonize, then you can
|
|
|
|
Center of you just don't want to bother with libpythonize, then you can
|
|
|
|
build Guidance with this command:
|
|
|
|
build Guidance with this command:
|
|
|
|
|
|
|
|
|
|
|
|
python setup.py install build_kcm --no-kcontrol
|
|
|
|
python setup.py install build_kcm --no-kcontrol
|
|
|
|
|
|
|
|
|
|
|
|
libpythonize is only needed for the KDE Control Center.
|
|
|
|
libpythonize is only needed for the TDE Control Center.
|
|
|
|
|
|
|
|
|
|
|
|
* You also need to have the development files from your X-server installed,
|
|
|
|
* You also need to have the development files from your X-server installed,
|
|
|
|
XFree86 or Xorg. Most distributions package these files up in a package
|
|
|
|
XFree86 or Xorg. Most distributions package these files up in a package
|
|
|
@ -112,7 +112,7 @@ As root run:
|
|
|
|
./setup.py install
|
|
|
|
./setup.py install
|
|
|
|
|
|
|
|
|
|
|
|
This will test for a working installation of PyQt/PyKDE and automatically
|
|
|
|
This will test for a working installation of PyQt/PyKDE and automatically
|
|
|
|
install the files using the same installation prefix as KDE. You will need
|
|
|
|
install the files using the same installation prefix as TDE. You will need
|
|
|
|
to have a working Python install before you can even run the setup.py script.
|
|
|
|
to have a working Python install before you can even run the setup.py script.
|
|
|
|
|
|
|
|
|
|
|
|
displayconfig-hwprobe installation
|
|
|
|
displayconfig-hwprobe installation
|
|
|
@ -147,9 +147,9 @@ inside displayconfig-hwprobe.py. Currently the hardware data is written to
|
|
|
|
|
|
|
|
|
|
|
|
Running
|
|
|
|
Running
|
|
|
|
-------
|
|
|
|
-------
|
|
|
|
Installation should add a couple of entries to the KDE Control Center in the
|
|
|
|
Installation should add a couple of entries to the TDE Control Center in the
|
|
|
|
System section (displayconfig will show up in Peripherals). It is also possible
|
|
|
|
System section (displayconfig will show up in Peripherals). It is also possible
|
|
|
|
to run the commands outside of the KDE Control Center from the shell as root:
|
|
|
|
to run the commands outside of the TDE Control Center from the shell as root:
|
|
|
|
|
|
|
|
|
|
|
|
* serviceconfig
|
|
|
|
* serviceconfig
|
|
|
|
* userconfig
|
|
|
|
* userconfig
|
|
|
|