-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installer updates #662
Installer updates #662
Changes from all commits
b7bd358
a3d53ea
435b4be
81517a9
8bb396d
16532fe
b8b08b5
3172b08
b866c29
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,82 @@ | ||
# Installation | ||
## Installation Script | ||
|
||
See https://github.com/nerdvegas/rez/wiki/Getting-Started#installation | ||
To install rez, download the source. Then from the root directory, run: | ||
|
||
``` | ||
]$ python ./install.py | ||
``` | ||
|
||
This installs rez to `/opt/rez`. See `install.py -h` for how to install to a | ||
different location. | ||
|
||
Once the installation is complete, a message tells you how to run it: | ||
|
||
``` | ||
SUCCESS! To activate Rez, add the following path to $PATH: | ||
/opt/rez/bin/rez | ||
|
||
You may also want to source the completion script (for bash): | ||
source /opt/rez/completion/complete.sh | ||
``` | ||
|
||
> [[media/icons/warning.png]] Do _not_ move the installation - re-install to a new | ||
> location if you want to change the install path. If you want to install rez for | ||
> multiple operating systems, perform separate installs for each of those systems. | ||
|
||
|
||
## Installation Via Pip | ||
|
||
It is possible to install rez with pip, like so: | ||
|
||
``` | ||
]$ pip install rez | ||
``` | ||
|
||
However, this comes with a caveat - rez command line tools _are not guaranteed | ||
to work correctly_ once inside a rez environment (ie after using the `rez-env` | ||
command). The reasons are given in the next section. | ||
|
||
Pip installation is adequate however, if all you require is the rez API, or you | ||
don't require its command line tools to be available within a resolved environment. | ||
|
||
Note that running pip-installed rez command line tools will print a warning like so: | ||
|
||
``` | ||
Pip-based rez installation detected. Please be aware that rez command line tools | ||
are not guaranteed to function correctly in this case. See | ||
https://github.com/nerdvegas/rez/wiki/Installation#why-not-pip-for-production | ||
for futher details. | ||
``` | ||
|
||
|
||
## Why Not Pip For Production? | ||
|
||
Rez is not a normal python package. Although it can successfully be installed | ||
using standard mechanisms such as pip, this comes with a number of caveats. | ||
Specifically: | ||
|
||
* When within a rez environment (ie after using the `rez-env` command), the rez | ||
command line tools are not guaranteed to function correctly; | ||
* When within a rez environment, other packages' tools (that were also installed | ||
with pip) remain visible, but are not guaranteed to work. | ||
|
||
When you enter a rez environment, the rez packages in the resolve configure | ||
that environment as they see fit. For example, it is not uncommon for a python | ||
package to append to PYTHONPATH. Environment variables such as PYTHONPATH | ||
affect the behaviour of tools, including rez itself, and this can cause it to | ||
crash or behave abnormally. | ||
|
||
When you use the `install.py` script to install rez, some extra steps are taken | ||
to avoid this problem. Specifically: | ||
|
||
* Rez is installed into a virtualenv so that it operates standalone; | ||
* The rez tools are shebanged with `python -E`, in order to protect them from | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If the |
||
environment variables that affect python's behaviour; | ||
* The rez tools are stored in their own directory, so that other unrelated tools | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And finally, due to explicit control over the environment, this would also go away. Pof! |
||
are not visible. | ||
|
||
Due to the way standard wheel-based python installations work, it simply is not | ||
possible to perform these extra steps without using a custom installation script. | ||
Wheels do not give the opportunity to run post-installation code; neither do | ||
they provide functionality for specifying interpreter arguments to be added for | ||
any given entry point. |
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would possibly be addressed by the above as well.