mirror of
https://github.com/parchlinux/calamares.git
synced 2025-02-24 02:45:44 -05:00
Distribution-independent installer framework
0eb1f002db
Both the KPMCore and the ChoicePage -- asynchronously -- were connected to the nextStatusChanged() signal. So if the core said next was true, that could end up communicated to the ViewManager, enabling the *next* button in the UI. Changing to the *erase* page generally triggers a KPMCore reload, which later emits a `hasRootMountPointChanged()` signal, once the layout is applied and the disk gets a root mount point. So we'd get a `true` from KPMCore, which -- because it was connected directly to the signal to the VM -- would override any other considerations. Hook up both signals to an intermediate slot that just recalculates whether the next button should be enabled, based on the state both of the Choice page and whatever else. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| .tx | ||
| 3rdparty | ||
| ci | ||
| CMakeModules | ||
| data | ||
| lang | ||
| LICENSES | ||
| man | ||
| src | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| AUTHORS | ||
| calamares.desktop | ||
| calamares.desktop.in | ||
| CalamaresConfig.cmake.in | ||
| CHANGES | ||
| cmake_uninstall.cmake.in | ||
| CMakeLists.txt | ||
| com.github.calamares.calamares.policy | ||
| Dockerfile | ||
| io.calamares.calamares.appdata.xml | ||
| LICENSE | ||
| README.md | ||
| settings.conf | ||
Calamares: Distribution-Independent Installer Framework
| Report a Bug | Translate | Contribute | Freenode (IRC): #calamares | Wiki |
|---|
Dependencies
Main:
- Compiler with C++14 support: GCC >= 5 or Clang >= 3.5.1
- CMake >= 3.3
- Qt >= 5.9
- yaml-cpp >= 0.5.1
- Python >= 3.3 (required for some modules)
- Boost.Python >= 1.55.0 (required for some modules)
- KDE extra-cmake-modules >= 5.18 (recommended; required for some modules; required for some tests)
- KDE Frameworks KCoreAddons (>= 5.58 recommended)
- PythonQt (optional, deprecated)
Individual modules may have their own requirements; these are listed in CMake output. Particular requirements (not complete):
- fsresizer KPMCore >= 3.3 (>= 4.1 recommended)
- partition KPMCore >= 3.3 (>= 4.1 recommended)
- users LibPWQuality (optional)
Building
See wiki for up to date building and deployment instructions.