mirror of
https://github.com/gryf/wicd.git
synced 2026-01-28 03:05:45 +01:00
Experimental: Apply changes involving setup.py
* Added setup.py from trunk * Updated various information files (AUTHORS, README, etc) * Update the Wicd icon * Move stuff around to match trunk's layout
This commit is contained in:
47
INSTALL
47
INSTALL
@@ -1,14 +1,39 @@
|
||||
To install, just run:
|
||||
sudo python setup.py install
|
||||
Installation of Wicd should be done using your distribution package if one
|
||||
exists. If not, the installation is relatively straightforward.
|
||||
|
||||
For now almost all the files and directories are dumped to /opt/wicd, though
|
||||
it's possible for the user to specify a different directory by editing two files;
|
||||
setup.cfg, and wpath.py. Simply change all mentions of /opt/wicd in those files
|
||||
to the directory of your choice.
|
||||
If you are installing from a subversion pull or beta/rc tarball and you want
|
||||
the native language translations, first run this:
|
||||
python setup.py get_translations
|
||||
You will not need to do this if you're installing from a release tarball.
|
||||
|
||||
It should also be noted that wicd also installs some files elsewhere, namely
|
||||
init.d and suspend.d scripts, dbus configuration files, and pixmaps. Exactly
|
||||
what gets put where can be viewed by opening up and reading setup.py.
|
||||
Next, configure Wicd for installation. Wicd will, by default, follow the
|
||||
FHS guidelines <http://www.pathname.com/fhs/> (or distribution standards
|
||||
where applicable if we know about them and it's feasible to implement them).
|
||||
You can specify exactly where every non-Python file (and some Python files)
|
||||
in Wicd will be placed. Pass "--help" as an option to the following command
|
||||
for more information, otherwise run it as is to configure Wicd for installation.
|
||||
python setup.py configure
|
||||
|
||||
Finally, do the actual installation. This step will need to be done as
|
||||
root or with sudo in most cases:
|
||||
python setup.py install
|
||||
If you are packaging Wicd, you will almost surely want to use the "--root"
|
||||
option; for example:
|
||||
python setup.py install --root=/package-dir
|
||||
|
||||
To uninstall, you can use (using root or sudo):
|
||||
python setup.py uninstall
|
||||
|
||||
You *MUST* run "python setup.py configure" before "python setup.py install" -
|
||||
the "configure" step generates wpath.py from wpath.py.in using the paths
|
||||
specified from the arguments to "python setup.py configure".
|
||||
As noted above in the configure step, "python setup.py configure" will use
|
||||
acceptable defaults, so it is usually not necessary to specify any arguments
|
||||
at all.
|
||||
|
||||
After installation, especially if Wicd has not been installed before, you
|
||||
will probably need to restart the system message bus (dbus) or reload its
|
||||
configuration. You will also need to make sure the Wicd init script is
|
||||
started at boot. How to do those things is distribution-dependent, so if
|
||||
you're not sure, ask in your distribution's support area(s).
|
||||
|
||||
In the (near) future, all the files will not all be put in one directory, and will
|
||||
instead follow linux standards for directory structure.
|
||||
|
||||
Reference in New Issue
Block a user