Install requires access to /opt/graphite

[awestendorf]

This makes sense for system installs but does not allow for virtualenv installs. The binaries are libraries should end up in the vritualenv path, and then the creation of a storage and conf directory can be left to the user. A simple message that one can see from pip would be enough to let them know that they have to create the directory.

[awestendorf]

The path problem also means that whisper has to be installed with sudo, though it can be installed correctly into a virtualenv.

[kristaps]

+1 What was the rationale behind the current behavior?

[drawks]

+1 I've never been a fan of the default configured installation path. I roll my own packages and the first thing I did was modify setup.py and setup.cfg to behave in a more standard way.

[techdragon]

+1 Im still scratching my head on 'opt' for this software. Its python! Im utterly stumped why its not virtualenv and config files.

[Whitespace]

I'm quite surprised that it's 2015 and this is still an issue :(

[mleinart]

Protip: making volunteer maintainers feel bad isn't a great way to get
progress on an issue

On Tue, Mar 31, 2015 at 5:46 PM, Tom Clark notifications@github.com wrote:

I'm quite surprised that it's 2015 and this is still an issue :(

—
Reply to this email directly or view it on GitHub
#74 (comment)
.

[timbunce]

And asking how you can help is a great way to move the issue forward.

[piotr1212]

See #835

[twm]

For anyone stumbling across this, you can set the GRAPHITE_NO_PREFIX environment variable to disable the /opt/graphite stuff.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[twm]

This is still a thing AFAIK.

[piotr1212]

setting the GRAPHITE_NO_PREFIX env variable ommits /opt/graphite. We also have #835 (comment) open, closing this issue to centralise discussion.