Skip to content
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

Investigate porting installation to setuptools. #32

Closed
tohojo opened this issue May 20, 2015 · 3 comments
Closed

Investigate porting installation to setuptools. #32

tohojo opened this issue May 20, 2015 · 3 comments

Comments

@tohojo
Copy link
Owner

tohojo commented May 20, 2015

Related to #30 -- is it worth converting to setuptools entirely?

@tohojo
Copy link
Owner Author

tohojo commented May 22, 2015

Setuptools does not allow installing arbitrary files (man page etc), so skip that for now.

@tohojo tohojo closed this as completed May 22, 2015
@dtaht
Copy link
Collaborator

dtaht commented Jun 10, 2015

There is a (new) requirement that this be present in an installation. I also am seeing things kind of leak over from the mac way of sticking stuff into /Frameworks instead of the linux way of LSB.

@tohojo
Copy link
Owner Author

tohojo commented Jun 10, 2015

Yes, setup.py is now fully setuptools-based. Turned out to work okay; it's where Python packaging is going / has gone.

When installing from the git dir, man page etc may not be installed by python setup.py install. In that case, run make install instead, that should put the static files given the right PREFIX (which defaults to /usr).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants