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

Fix‐up setup.py #4

Open
johndrinkwater opened this issue Aug 8, 2018 · 3 comments
Open

Fix‐up setup.py #4

johndrinkwater opened this issue Aug 8, 2018 · 3 comments

Comments

@johndrinkwater
Copy link
Owner

Either move to the modern method, or discover how to make setup mung the launch script for the various installation locations the user could pick (--user, --prefix, etc)

With how the current script is designed, it file‐copies everything in anoise/ into a share/anoise location and the bin assumes the location; most python tools that use this method don’t copy the ‘module’ files like this, so can just rely on import to transclude the relevant files.

@johndrinkwater
Copy link
Owner Author

Looked into this as part of https://bugs.launchpad.net/anoise/+bug/1528449 and it aint just as simple as fixing those /usr/ prefixes in the data [].

@johndrinkwater
Copy link
Owner Author

@johndrinkwater
Copy link
Owner Author

More info on this: will need to bindtextdomain('anoise', locale_dir) to make it not use system-wide translations, a further adjustment required for setup.py

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

No branches or pull requests

1 participant