-
Notifications
You must be signed in to change notification settings - Fork 5
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
Decouple from el-get #19
Comments
I don't think El-get is complicated, but it do complex actions. Also requires In most cases package.el is OK, so lets make First step was adding I think now we need to give users possibility to choose what library to use to manage packages: stock Then modify README according this. And do something with |
You may not know this, but I was a major contributor to |
The first thing I did was to change to an Apache-like configuration where the "startup" files were all moved to a "startup-available" directory, and then I linked everything but 10-el-get.el into the "startup" directory. Does this make sense as a way to do configuration? |
Yes it make sense, but I think that creating of symlinks would be not so trivial task for MS Windows users. Also no changes should be made in cloned repo (or package dir) to customize I propose to move |
SGTM Sent from my moss-covered three-handled family gradunza
|
This is done, right? Should I close it? |
I move the file to "legacy", but some words need to be said in readme. |
el-get is kind of evil, but the README for elhome and elhome itself both use it.
The text was updated successfully, but these errors were encountered: