Whenever the target of an installation is a partition that is not empty, the Installer prompts the user whether they would like to continue with a 'clean installation', i.e. an installation that clears out the system folder, excluding the settings, and cleanly installs the assets in the source's system folder. At all other locations the source data is merged, meaning that the source version is copied in place. The logic that clears out the existing /system/ directory stopped working. This change moves that logic from the copying process, to where it is run before any file is copied. The added advantage is that the system folder is now properly cleaned up, also stray files under the system folder will be removed. This change does not change the logic of what constitutes a 'clean install'. There are arguments to be made that it should potentially also drop the settings files, as well as clean out the user's home folder for stray add-ons, but that really is different functionality, and at this points I think the requirements for that are not yet fleshed out. The change was manually tested. Fixes #16092 Change-Id: Ia6781c8d2330ba336b3921f9a980b5e31c48a2ec Reviewed-on: https://review.haiku-os.org/c/haiku/+/3140 Reviewed-by: Andrew Lindesay <apl@lindesay.co.nz>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.