Task #11328 (new)
Opened 11 years ago
Last modified 9 years ago
Decide on a policy for consdortium dependencies — at Version 1
| Reported by: | spli | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Testing and Docs |
| Component: | General | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | hflynn, jamoore, sbesson, imunro-x, khgillen |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | Testing and Docs (1) |
Description (last modified by spli)
If a consortium add on is installed server side (e.g. web-apps and server scripts) they may require third party dependencies such as Python modules, other compiled libraries, etc.
We should consider some guidelines on 'best practice'. For example, if we recommend using virtualenv should we also recommend the --system-site-packages flag? The advantage is that admins can install many OMERO dependencies using a distribution provided package instead of having to use pip and potentially deal with compilation problems (especially with numpy and scipy), and also means they won't unexpectedly get a major version bump. The disadvantage is that you can end up with an incompatible mix of modules.
See also https://github.com/openmicroscopy/omero_searcher/pull/9#issuecomment-21789327 onwards
Change History (1)
comment:1 Changed 11 years ago by spli
- Description modified (diff)
- Summary changed from Decide on a policy for server-side Python modules to Decide on a policy for consdortium dependencies
