Fix MELPA Stable dependencies on unreleased packages (#7) #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix
Package-Requires
header entry so that all the dependencies are available on MELPA Stable for future releases.This will have no effect if using MELPA as these version numbers refer to the minimum acceptable version and not to the actual downloaded version (except for MELPA Stable). MELPA packages are built directly from the latest package source code in the upstream repositories.
Use of MELPA Stable will be supported and tested for
verilog-ext
but not recommended as some of the released versions of the dependencies are a bit old (e.g.outshine 3.0.1
dates from Jan 2019). On top of that, according to https://github.com/melpa/melpa#melpa-stable: