-
Notifications
You must be signed in to change notification settings - Fork 21
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
WIP Replace flymake with flycheck #224
base: master
Are you sure you want to change the base?
Conversation
just checked out the branch and ran
|
I just want to push a WIP branch. :-) |
But I see whats the problem is. Because we just add package to vendor we would like to use, we have to add the dependencies by our self. Maybe we should think about that. Why do we lock packages via vendor? What would happened if we just work with package itself instead adding them as submodule. etc |
We decided to use vendored library to have full control over our dependencies. This allows us to keep them in sync and provide a known-working-state. You could probably achieve this by relying on package versions and dependency specifications but at the time when we started with cabbage, no package manager offered the needed flexibility. |
I really understand this point, maybe we could go with MELPA STABLE and pin specific packages to always get tagged packages from MELPA STABLE. |
@senny What do you think about the idea if we go with Cask and pinned packages? cask/cask#252 I know its a emacs 24.4 feature, but to be honest, people really should update, I mean REALLY. emacs 24.4 is in a really good shape. |
to be honest, this is not something I'd consider at this point. I don't want force cabbage users to to upgrade their Emacs at all times. A good amount of co-workers (including me) are still on Besides that, I'm not eager to move away from the submodule approach we have at the moment. It allows for precise control of what works together. In my experience what we have now works very well. I'd rather not depend on an external package for the backbone of this project. The experience cabbage should provide is:
@tonini I hope this makes any sense. |
@senny Thanks for this great explanation. :-) I really see and understand your point, so let's talk about some dependencies we have with The following packages are dependencies which we have to resolve. |
@tonini Is there anything preventing us from vendoring those in? |
@senny Not at all, I just wanted to hear a GO before vendoring them UP ;-) |
GO 🏁 |
@senny I'm working on it, had a little break last week. :-) |
No description provided.