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

Possible python setup.py path issues #273

Closed
mattpascoe opened this Issue Oct 5, 2012 · 0 comments

Comments

Projects
None yet
2 participants
@mattpascoe

mattpascoe commented Oct 5, 2012

While trying to build graphite packages I ran into the following situation. I have downloaded the latest graphite-web from github at the following path: https://github.com/graphite-project/graphite-web/tarball/master

If I run fpm -s python -t deb graphite-web-latest/setup.py I get a package that is trying to install everything into /usr/lib/python2.7/dist-packages/webapp.

If I run python setup.py -n install it would have installed everything into /opt/graphite.

So in an effort to fix the path issue, I run fpm like this:
fpm -s python -t deb -S 2.7 \ --python-install-bin /opt/graphite/bin \ --python-install-lib /opt/graphite \ --python-install-data /opt/graphite graphite-web-latest/setup.py

This fixes the issue such that it will now install into /opt/graphite as desired but there is a portion of it that is not properly pathed.

To fix that issue I must manually issue mv /opt/graphite/graphite* /opt/graphite/webapp after the .deb package is installed to get graphite to run properly.

My wild guess is that there is something in the setup.cfg/setup.py that is not getting interpreted correctly by fpm? Also due to my lack of python knowledge, I can't say if this is a graphite setup.py issue.

prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 18, 2014

jls
- python: only specify --install-{scripts,lib,data} if the
  attributes/flags are set in fpm.

  This should fix jordansissel#273 without breaking prior behavior.

prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 27, 2014

- python: only specify --install-{scripts,lib,data} if the
  attributes/flags are set in fpm.

  This should fix jordansissel#273 without breaking prior behavior.

jordansissel added a commit that referenced this issue Apr 24, 2015

- python: only specify --install-{scripts,lib,data} if the
  attributes/flags are set in fpm.

  This should fix #273 without breaking prior behavior.

jordansissel added a commit that referenced this issue Jun 20, 2016

- python: only specify --install-{scripts,lib,data} if the
  attributes/flags are set in fpm.

  This should fix #273 without breaking prior behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment