Description
List of all previous MELPA/ELPA issues in this repo
- Consider submitting to MELPA #5: Consider submitting to MELPA
- MELPA recipe? #27: MELPA recipe?
- Submit to MELPA? #29: Submit to MELPA?
- Is this on melpa? #51: Is this on melpa?
- Is the ELPA repository at http://joseito.republika.pl/sunrise-commander/ working? #57: Is the ELPA repository at [joseito.republika.pl] working?
Why SC was removed from MELPA
SC was added to MELPA in 2012: melpa/melpa#153
But removed in 2013: melpa/melpa#602
Relevant remarks from the removal thread:
the extension source files are not currently set up correctly for packaging. Each one should have have a dependency line similar to
;; Package-Requires: ((sunrise-commander "6"))in its comment header.
You might consider filing a pull request with the sunrise-commander project to add these headers, or (strongly preferable) suggest that the author provide a way to disable extensions even when they are available.
I've looked at the sunrise-commander source code, and I can't see any code which automatically loads the extensions if present. In fact, the doc headers for the extensions say that they should be explicitly required in order to enable them.
the code is in the extensions, except the
...-checkpointsextensions all have a magic autoload comment at the end.
the options are either:
- Remove those autoload lines (preferred solution) or...
- Add
Package-Requiresheaders to all the extensions
The
sr-extend-withfunction should be responsible for trying to load the extensions .el for the given name. It's fine to package all the extension but the author should meet us halfway and remove the autoloads.
It is not too weird to have a an extensible plugin include a default set of plugins. Yasnippet includes a default set of snippets. We don't package them separately.
Conflicting extensions used to be installed by the bundle in MELPA
Well, actually that looks like a problem with the bundle installed by MELPA: it seems it's installing two extensions that are not totally compatible with each other: the popviewer extension (that makes the viewer window "pop up" in a separate frame) and the buttons extension. I would recommend at least for a start to disable one of them doing
M-x customize-variable [RET] sr-popviewer-enabled [RET]and toggling that flag off. In the long run, I'm planning to fix that small incompatibility between the two extensions, so you can have them both installed simultaneously without seeing weird effects like that.
Additionally, since MELPA has changed somewhat the rules of the game (by making all extensions, which were supposed to be optional, the default) I've changed the default value of the
sr-popviewer-enabledflag to false in order to make the choice between regular and popped viewer apparent to new users.