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

Should probably move to el-get? #112

Open
gabrielelanaro opened this issue Mar 10, 2013 · 1 comment
Open

Should probably move to el-get? #112

gabrielelanaro opened this issue Mar 10, 2013 · 1 comment
Labels

Comments

@gabrielelanaro
Copy link
Owner

el-get seems to support a whole lot of packages and emacs-for-python can probably benefit from having an installer that keeps all the packages updated.

Advantage:
simplified structure, epy has to include only customization and not packages.
packages update by themselves

Disadvantages:
packages become not easily patchable
each time a package fail, epy fails. Less control and probably less stability

@MortalCatalyst
Copy link

I would agree. It would be good if elget had a requires options so could choose component set that works.

ipython==some_version etc like requirements file.

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

No branches or pull requests

2 participants