Noam Postavsky
Noam Postavsky
> As an alternative, would it be possible for the MELPA el-get to leave itself installed but remove itself from load-path and then reload el-get, thus pulling in the "real"...
> So does that mean I'm correct that no other MELPA package should declare a dependency on el-get? Yeah, I think so.
I've been looking at this. When installing a package we do `download+unpack+build+init` dependencies, `download+unpack+build+init` the package. To get auto dependency we would need to do `download+unpack` the package, check `Package-Requires`,...
There's an additional problem that `Package-Requires` may refer to different package names than those that el-get knows about. For example, magit is split into `magit`, `magit-popup`, and `with-editor`. So we'll...
Yes, there is a solution for this in #2264 (but it's not quite ready yet), see also https://github.com/dimitri/el-get/pull/2238#issuecomment-138383276
I think the main difficulty would be compiling the `file extension -> package` list. I don't see a way to automate it short of installing every package which would really...
I'm not sure if semi-automatic is better than fully manual: typing `M-x el-get-auto-mode` vs `:auto-mode ".foo"`
Yes, that is what I was thinking too. I'm just not sure invoking a helper function would be faster/easier than typing in the autoinstall info directly.
Where do people download nxhtml from then?
Not currently, no. You'll have to copy the depends from the original recipe.