Dimitri Fontaine
Dimitri Fontaine
That is a good complementary idea, I think.
Please prepare a patch, I will accept fixing the keybindings to be more like `dired` and the like.
Please provide in more details what you did to install.
el-get is already able to use more than 1 directory where to lookup for recipes, see `el-get-recipe-path`. So maybe we could have a "testing" path and a "stable" path, and...
Good point about the dependencies, and this `:variant` looks too complex an implementation for the problem at hand. Currently only the `:name` property works that way (matching rather than overloading)....
It seems that we need to move to multiple variants support here. I wonder if we should prefer having them in separate directories or as separate list entries in the...
What about forcing the dependencies to be solved only using recipes of the same variant? That would mean that if package a variant devel depends on package b variant stable...
My view on el-get recipes is that whoever submits a Pull Request for a recipe is an actual user of the package and is proposing a version that is known...
I don't think we can find an easier solution than updating the dependencies in such a case.
Usually what we do is that when we see a missing dependency, we turn the automated recipe into a manually managed one, which will have the priority thanks to `el-get-recipe-path`.