MYOB > Your idea about solving hotfixes with seldomreleased “servicepacks” R1, R2 and so on is likely cause a lot of frustration for users connected 24/7 (well… 24 hours, 7 days a week). I would definitely want a hotfix immediately. There is no problem in having an updater IF the hotfixes/bugfixes etc. are coded properly.And the risk for breaking the API is in no way smaller with “servicepacks”, just look at SP2 for WinXP (I feel sorry for those who have to use XP… I run Win2K and FC2 as dualboot, with linux as default OS - since I can’t run BEOS on a duron anyway
)
I don’t see the problems with dependencies (on Haiku that is), after all I’ve used windoze for years (against my will… couldn’t get OS/2 running… and you know… the games… the primary reason to have a Windoze system installed…
… productivity belongs to another platform, be it Haiku (in the future) or linux-distros or mac or whatever… anything but windoze for productivity), but in Windows you often have to install app#2 if you want app#1 to work. Many apps wont work without IE and don’t forget the whole problem with “can I uninstall this DLL or not?? oh I don’t know… I guess I have to let it be…” - I mean… Just look at the mess in any Windoze system folder…
As long as the setup-system is created in a clever way dependencies wont be a problem.
Anyway… the updater spoken of in this thread is apparently meant only for OS-updating and backwordscompatibility shouldn’t be a problem, unless we are talking about a severe bug, in which case the system would probably be unbootable without the fix, why nobody has to worry about dependencies and backwordscompatiblity when it comes to OS-updates.
My idea of a update-solution would be something like synaptic for FC2. (Those who don’t know synaptic I can say it’s a frontend for apt-get…)
Well… perhaps I should explain it differently.
- The user should have an update-client.
- This update-client connects to the update-server.
- The client sends information about hardware and software to the server.
- The server sends information back regarding available updates.
- The user chooses which updates to download and/or install.
- The client downloads updates from the server.
- The client may install the updates (or this can be done manually).
This way of doing it should be firewall-friendly. At least for software firewalls installed at the user’s own pc.
It shouldn’t be exactly like synaptic since it has a less-intuitive GUI… or perhaps I should say it isn’t too easy to understand.
The system-updater should be pretty configurable. E.g. have some advanced settings, where the user could add more servers so all updates (incl. updating and/or installing of 3rd party apps from other servers) could be done thru this updater. However, as a default only the OS-update-server should be available. Other servers should only be added by the user.
Perhaps an API could be/should be created for this purpose? I mean an InstallApplication-something-API?
In case this (in Haiku R2) should require root-status / Admin-rights, then this could be enabled pretty much as in linux (-su root or in synaptic just write password in the popup-window when you try to update your system while being logged on as normal user). In windows you have to log off as user and log on as admin to update your system - this is bothersome for most people, right?
Damn… I shouldn’t have had access to the forum, I just do looooong entries… ![:stuck_out_tongue: :stuck_out_tongue:](https://discuss.haiku-os.org/images/emoji/twitter/stuck_out_tongue.png?v=5)
BTW: Thanks Kurtis, for activating my profile … I’m in!!! I’m in!!! ![:smiley: :smiley:](https://discuss.haiku-os.org/images/emoji/twitter/smiley.png?v=5)