-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Add zap stanza for Paragon Casks #16458
Comments
That one. Otherwise we’d have a confusing ever-expanding list. Care to submit the PR? |
I plan to submit a PR, however I just realized that if a zap stanza only touched files from the most recent known For example, the use case:
|
You are correct. However, that is a limitation of the system as it works currently. In the future, we’d like to have glob support (i.e. As we don’t support it yet, we have to keep only the newer versions. You can do something like this, though. It won’t work for any version currently, but will be ready for when the feature lands. |
|
@Haodong Next time, open up an new issue. Your error is unrelated. Fixed in #16474 |
No need to keep this open anymore. Question has been answered. |
References #7327
The current uninstall stanzas for cask paragon-ntfs and cask paragon-extfs leave some files and folders on the system in preparation for a re-install later. A zap stanza would be needed to eliminate these files and folders.
It is not clear to me why paragon-ntfs references two similar preference pane plists; I expect one of them is from an older version of paragon-ntfs.
Should a zap stanza remove all known instances of historical installations, or should a zap stanza only touch files that the most recent known
brew cask install paragon-ntfs
would create?The text was updated successfully, but these errors were encountered: