Notes |
|
|
Do we deprecate this feature? If so, I can make a changelog notification of deprecation akin to SemVer (although we don't follow SemVer).
|
|
|
(0019954)
|
Zalewa
|
2018-10-06 16:56
(edited on: 2018-10-06 16:58) |
|
I think we can safely remove it outright. (EDIT: we will have to keep the service on our server for some time, tho, at least for a few months after 1.2 release)
One thing to keep in mind is that "Auto Updates" page in the config box will now become empty on Linux and we will need to hide it. (that's actually a good thing, BTW, because this page had just one checkbox on Linux and it just looked silly)
Blzut, do you agree with the removal?
|
|
|
(0019971)
|
Blzut3
|
2018-10-06 21:37
|
|
The Mac autoupdater is being disabled due to Apple policies getting in the way of what we're currently doing. So relying on Mendeley is not an option. |
|
|
(0019974)
|
Blzut3
|
2018-10-07 00:56
|
|
Thought of another reason to keep IP2C on a separate updater: Is this really something that needs super user privileges to be able to update? |
|
|
(0019975)
|
Zalewa
|
2018-10-07 05:54
|
|
Quote from Blzut3 Thought of another reason to keep IP2C on a separate updater: Is this really something that needs super user privileges to be able to update?
Well, it would anyway if we were to go with the original request to rely on the readily-available geolite package from the Linux package manager.
Still...
Quote from Blzut3 The Mac autoupdater is being disabled due to Apple policies getting in the way of what we're currently doing. So relying on Mendeley is not an option.
... this pretty much disqualifies the removal anyway. The matter is concluded for me: "IP2C Update" stays. Let's return the focus on how to satisfy the licensing requirements. |
|