Repository navigation
build: package the plasmoid as a ZIP archive - #14
Merged
Merged
Conversation
KPackage 6 opens a .plasmoid with KZip only. kpackagetool6 — and the Plasma "Get New Widgets" installer behind it — rejects a gzip tarball outright with "Could not open package file". make build produced a tarball, so the package the release workflow published could not be installed by anyone; make install, which installs from the directory, hid this. make build now writes a ZIP with entries relative to the applet root, and the packaging test asserts the container format so it cannot regress. Verified: kpackagetool6 --install and --upgrade both succeed from the archive and the installed tree is byte-identical to the source.
This file contains hidden or 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
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.
KPackage 6 opens a .plasmoid with KZip only. kpackagetool6 — and the Plasma
"Get New Widgets" installer behind it — rejects a gzip tarball outright with
"Could not open package file". make build produced a tarball, so the package
the release workflow published could not be installed by anyone; make install,
which installs from the directory, hid this.
make build now writes a ZIP with entries relative to the applet root, and the
packaging test asserts the container format so it cannot regress. Verified:
kpackagetool6 --install and --upgrade both succeed from the archive and the
installed tree is byte-identical to the source.