incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <>
Subject [jira] [Commented] (AMBARI-1779) Remove hard references to /usr/lib/pythonX.Y/site-packages from all files (shell scripts, java, poms, python)
Date Wed, 10 Apr 2013 06:22:24 GMT


Mahadev konar commented on AMBARI-1779:

[~tmckay] the issue is that a pyton2 executable is not standard. It might work on fedora 18.
Instead of python2 why dont we just use python and just make sure its > 2.0. The patch
attached will cause issues on different platforms (lets say on a mac, there is no python2).
Does that make sense? 

Also for changing the structure, we will also have to do some post install changes wherein
the prior configs that have some paths in there that reference old 2.6/site packages are upgraded
to new ones when you upgrade the agent.
> Remove hard references to /usr/lib/pythonX.Y/site-packages from all files (shell scripts,
java, poms, python)
> -------------------------------------------------------------------------------------------------------------
>                 Key: AMBARI-1779
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.2.0
>         Environment: Fedora 
>            Reporter: Trevor McKay
>             Fix For: 1.3.0
>         Attachments: ambari_build.patch
> Hard references to /usr/lib/pythonX.Y/site-packages should be eliminated from the build
process and java/runtime scripts for portability.
> Any python modules in site-packages should be importable (ie, a proper package) and will
be found on the standard python path.  Therefore, any code that needs to be run from those
modules can be run with python wrapper scripts located in /usr/bin or /usr/sbin (for example)
without an explicit path reference.
> Python code in site-packages that is not importable should be made so and run from a
wrapper, or it should be relocated (to /usr/lib/exec/ambari, for example)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message