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.
PR Summary
The information in
<name>-pkg.el
did not agree with the information in<name>.el
. This pull-requests addresses that be removing the outdated<name>-pkg.el
.While the end-user package manager
package.el
expects a file<name>-pkg.el
, this should only be generate by the package archive (such as GNU ELPA and MELPA), instead of being tracked in the upstream repository.The tools used maintain the various *ELPA, do not use
<name>-pkg.el
as a data source, they only generate it it.elpa-admin.el
, the tool used for GNU ELPA and NonGNU ELPA, does not use<name>-pkg.el
as a data source and it never has.package-build.el
, the tool used for Melpa, prefers<name>.el
but currently falls back to get information missing from there from<name>-pkg.el
instead. I am goint to change that; soon<name>-pkg.el
will be ignored as a data source by this tool too.PR checklist