-
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
Iterative update #17
Comments
@PVince81 technically I see no problem with that. update Url provided by http://apps.owncloud.com/updater.php?version=6x0x2x0x1399658401.0121x1405698422xstablexx2014-06-24T15:11:49+00:00 etc... UPD. I mean no changes in the current app code is required |
there is no magic at all. Core fetches the feed from apps.owncloud.com and thakes a link to a new package from this feed |
Proof: That's what we suggest for 4.5.0 users
|
So, this can be closed? |
@te-online Yes, i think this could be closed as this just needs to be fixed at updater url level as discussed in owncloud/appstore-issues#4 |
@PVince81 closing this issue as it is better to implement on the update server side |
@VicDeo Its already implemented at the update server side: owncloud/appstore-issues#4 :-) E.g. 8.1.7 gets 8.1.9: before 8.1.9 gets 8.2.7: |
@schiesbn is suggesting that for people who use the updater app, the update should be iterative: 6.0.1 then 6.0.2 then 6.0.3, etc to make sure that all update scripts run in the correct order because some scripts might only run for example between 6.0.2 and 6.0.3.
This is mostly assuming that the updater app is used by less tech-savvy people.
Such iterative update path is not possible when using distro package managers.
I'm not convinced that it's a good idea and think that update code needs to support update paths like 6.0.1 to 6.0.4.
But let's discuss @karlitschek
The text was updated successfully, but these errors were encountered: