Add a function for building ELPA-compatible package archives #175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akirak
force-pushed
the
build-elpa-archive
branch
2 times, most recently
from
d48bd4a to
83b7d44
Compare
akirak
force-pushed
the
build-elpa-archive
branch
from
83b7d44 to
675976b
Compare
|
I don't want to implement this feature as part of this repository. I will create a separate repository for this experimental feature. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an experimental feature for providing packages to platforms that don't support Nix (e.g. Windows without WSL).
With
lib.buildElpaArchivefunction exposed from the flake, it builds a package archive that can be installed usingpackage-install-file. The function takes the value ofpackageInputs.*attribute and builds a directory that contains the Emacs Lisp source files and*-pkg.elfile in the same directory, so you can upload the artifact to a server. You also need to add a writable permission.This is a fallback for non-Nix platforms. It is not recommended to use it daily, as there are extra overheads than the existing solution.