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
Make FretWork working in a package/dependencies management system (well… any linux distro :p ) #43
Comments
I vote for the git submodule approach |
Yeah I would agree with that ! |
Fretwork should work with pip as it is(a sort of package manager), I have precompiled wheels for windows. On linux you can just install from the source package with pip (should work on osx as well with xcode installed). Plus when we finish getting virtualenv setup all of this should be simplified. I don't really like git submodules to much, I always forget to update them, and to run the extra command when cloning... |
Hum… Well we could create a fretwork AUR package that would install itself inside python2/site-packages (just like with pip). Here is an example with python-cerealizer :
That allows to use the system package manager. |
https://aur.archlinux.org/packages/python2-fretwork-git |
Yeah that would work for those of us that use arch. Only gripe is that i was planning on using the "released" versions for the games and then making major changes on master and updating things when i put a new release out. |
Well the AUR package can track a specified branch, like a "release" one. |
true |
Well, basically, I'm using Manjaro (Arch-based), and there is already a fofix package (https://aur.archlinux.org/packages/fofix-git, build from git clone of this repo).
What would be best :
I can create the package for AUR, that's something I already did. But YOU know how you created fretwork so what would be best.
The text was updated successfully, but these errors were encountered: