graphite-dev team mailing list archive

[Andrew Meyer <question401544@xxxxxxxxxxxxxxxxxxxxx>]

New question #401544 on Graphite:
https://answers.launchpad.net/graphite/+question/401544

While attempting to automate installation of a Graphite server with Puppet, I noticed the following behavior:

When I install Carbon and Graphite Web from the default pip package repository, PyPI, the packages are installed by default to `/usr/local/lib/python2.7/dist-packages/`. For example:

    pip install carbon==0.9.15
    pip install graphite-web==0.9.15

results in packages installed to the following directories (on Ubuntu 16.04 LTS):

    /usr/local/lib/python2.7/dist-packages/carbon-0.9.15.dist-info/
    /usr/local/lib/python2.7/dist-packages/graphite_web-0.9.15.dist-info/

However, when I instead install the _exact_ same versions of Carbon and Graphite Web from GitHub:

    pip install https://github.com/graphite-project/carbon/tarball/0.9.15
    pip install https://github.com/graphite-project/graphite-web/tarball/0.9.15

The packages end up in `/opt/graphite`:

   /opt/graphite/webapp/graphite_web-0.9.15-py2.7.egg-info/
    /opt/graphite/lib/carbon-0.9.15-py2.7.egg-info/

Why is this? Why does it matter where I'm getting the package from given that I'm installing the exact same version of each package (0.9.15) each time? Is there a way to get the `/opt` style installation behavior using the regular PyPI packages?

-- 
You received this question notification because your team graphite-dev
is an answer contact for Graphite.