diff options
| author | Florian Bruhin <me@the-compiler.org> | 2021-02-04 10:13:09 +0100 |
|---|---|---|
| committer | Florian Bruhin <me@the-compiler.org> | 2021-02-04 10:13:09 +0100 |
| commit | 565c1c1cd9d8393af9585964eb48f01c1800a23f (patch) | |
| tree | f2659874ead4b3d7ac1f8fc75903cad12a1c8443 /doc/install.asciidoc | |
| parent | a04976c4841b91798d6276235a476e230fff17c4 (diff) | |
| download | qutebrowser-565c1c1cd9d8393af9585964eb48f01c1800a23f.tar.gz qutebrowser-565c1c1cd9d8393af9585964eb48f01c1800a23f.zip | |
Improve mkvenv.py instructions
Diffstat (limited to 'doc/install.asciidoc')
| -rw-r--r-- | doc/install.asciidoc | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/install.asciidoc b/doc/install.asciidoc index b78e74d07..8dd15802d 100644 --- a/doc/install.asciidoc +++ b/doc/install.asciidoc @@ -427,7 +427,7 @@ See the next section for an alternative install method which might help with those issues but result in an older Qt version. You can specify a Qt/PyQt version with the `--pyqt-version` flag, see -`mkenv.py --help` for a list of available versions. By default, the latest +`mkvenv.py --help` for a list of available versions. By default, the latest version which plays well with qutebrowser is used. NOTE: If the Qt smoke test fails with a _"This application failed to start @@ -482,8 +482,10 @@ $ python3 scripts/asciidoc2html.py Updating ~~~~~~~~ -When you updated your local copy of the code (e.g. by pulling the git repo, or -extracting a new version), the virtualenv should automatically use the updated -code. However, dependencies won't be updated that way. Thus, it's recommended -to run `mkvenv.py --update` instead, which will run `git pull` and recreate the -virtualenv with updated dependencies. +If you cloned the git repository, run `mkvenv.py --update` which will take care +of updating the code (via `git pull`) and recreating the environment with the +newest dependencies. + +Alternatively, you can update your local copy of the code (e.g. by pulling the +git repo, or extracting a new version) and the virtualenv should automatically +use the updated versions. However, dependencies won't be updated that way. |