-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Allow upgrades #16
Labels
Enhancement
New features or functionality
Comments
Right now, upgrades don't work. You can't do them. What we will be doing is:
This means mods have to be clear up-front about which files need to be kept between releases, and makes the upgrade process much more predictable. I don't think we should allow unzip in place. |
I have implemented this (except the preserved files part) in #83 |
RichardLake
pushed a commit
to RichardLake/CKAN
that referenced
this issue
May 30, 2015
Remove Core tests from the GUI.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At some point, people are going to want to upgrade their mods. There are two ways this is commonly done:
The first means one knows exactly what one should end up with, the second means we can more easily preserve state generated by a previous install (although #15 provides a potential way of doing this).
We need to decide what the default behaviour is (right now it's unzip-in-place), but give the option to delete everything and unzip afresh.
The text was updated successfully, but these errors were encountered: