-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packaging (exporting) operation is not idempotent #611
Comments
What's that |
A related issue: The |
It's a way to pass "data" to IPM commands. You're right that it's not documented and we will probably deprecate such usage in favor of |
Is there any reason we keep the directory in addition to the tarball or shall I go ahead and remove it? If we remove it, we probably solve the main thread issue as well. |
@isc-shuliu I can't think of a reason to keep it so best to remove the directory since only the tarball is needed for both packaging and publishing. A user can always unpack the tarball to view the directory structure |
Also consider the case when the package tar file already exists. Automatic overwrite or something else? I don't see here a clear winner as long as the behavior is documented. |
When running
zpm-registry package -only -DPath=/tmp/exported/zpm-registry -verbose
for the first time, it creates a folder and a tarballHowever, when subsequently running the command for a second time, 4 more files are created:
The text was updated successfully, but these errors were encountered: