Arch Linux User Repository

@electricprism It's different, Maui Shell is a Nitrux project.

• https://youtu.be/gSX4rNr14Vg
• https://github.com/Nitrux/maui-shell
• https://nxos.org/maui/introducing-maui-shell/

Is this different from Plasma Mobile ? I've noticed it's not present on the Maui Project repos -- https://invent.kde.org/maui?filter=shell

@ManuelBoe I've just push new maui-core-git to AUR and add it to depends list in this commit, You can test it and hopefully no more error.

build fails: Could not find a package configuration file provided by "MauiCore"

full log:

 CMake Error at CMakeLists.txt:20 (find_package):
  By not providing "FindMauiCore.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "MauiCore",
  but CMake did not find one.

  Could not find a package configuration file provided by "MauiCore" with any
  of the following names:

    MauiCoreConfig.cmake
    mauicore-config.cmake

  Add the installation prefix of "MauiCore" to CMAKE_PREFIX_PATH or set
  "MauiCore_DIR" to a directory containing one of the above files.  If
  "MauiCore" provides a separate development package or SDK, be sure it has
  been installed.

@LuckyTurtleDev I've just push new cask-server-git to AUR and add it to depends list in this commit, You can test it and hopefully no more error.

build fail, with Could not find a package configuration file provided by "CaskServer"

full log:

==> Starting build()...
-- The C compiler identification is GNU 12.1.1
-- The CXX compiler identification is GNU 12.1.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Gettext: /usr/bin/msgmerge (found version "0.21")
-- Found KF5I18n: /usr/lib64/cmake/KF5I18n/KF5I18nConfig.cmake (found version "5.96.0")
-- Found KF5Config: /usr/lib64/cmake/KF5Config/KF5ConfigConfig.cmake (found version "5.96.0")
-- Found KF5Service: /usr/lib64/cmake/KF5Service/KF5ServiceConfig.cmake (found version "5.96.0")
-- Found KF5: success (found suitable version "5.96.0", minimum required is "5.60") found components: I18n Config Service
CMake Warning at CMakeLists.txt:18 (find_package):
  By not providing "FindCaskServer.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "CaskServer", but CMake did not find one.

  Could not find a package configuration file provided by "CaskServer" with
  any of the following names:

    CaskServerConfig.cmake
    caskserver-config.cmake

  Add the installation prefix of "CaskServer" to CMAKE_PREFIX_PATH or set
  "CaskServer_DIR" to a directory containing one of the above files.  If
  "CaskServer" provides a separate development package or SDK, be sure it has
  been installed.


CMake Warning at /usr/share/ECM/kde-modules/KDEInstallDirsCommon.cmake:382 (message):
  KDE_INSTALL_BINDIR, KDE_INSTALL_LIBDIR and KDE_INSTALL_INCLUDEDIR should
  either all be absolute paths or all be relative paths.
Call Stack (most recent call first):
  /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:223 (include)
  /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include)
  CMakeLists.txt:20 (include)


-- Installing in the same prefix as Qt, adopting their path scheme.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
CMake Warning at /usr/share/ECM/kde-modules/KDEInstallDirsCommon.cmake:382 (message):
  KDE_INSTALL_BINDIR, KDE_INSTALL_LIBDIR and KDE_INSTALL_INCLUDEDIR should
  either all be absolute paths or all be relative paths.
Call Stack (most recent call first):
  /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:223 (include)
  /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include)
  casklib/CMakeLists.txt:29 (include)


-- Could not set up the appstream test. appstreamcli is missing.
-- Found X11: /usr/include
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found KF5KIO: /usr/lib64/cmake/KF5KIO/KF5KIOConfig.cmake (found version "5.96.0")
-- Found KF5: success (found suitable version "5.96.0", minimum required is "5.60") found components: I18n Service KIO
CMake Error at casklib/CMakeLists.txt:76 (find_package):
  By not providing "FindCaskServer.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "CaskServer", but CMake did not find one.

  Could not find a package configuration file provided by "CaskServer" with
  any of the following names:

    CaskServerConfig.cmake
    caskserver-config.cmake

  Add the installation prefix of "CaskServer" to CMAKE_PREFIX_PATH or set
  "CaskServer_DIR" to a directory containing one of the above files.  If
  "CaskServer" provides a separate development package or SDK, be sure it has
  been installed.


-- Configuring incomplete, errors occurred!
See also "/home/lukas/.cache/yay/maui-shell-git/src/build/CMakeFiles/CMakeOutput.log".

@ManuelBoe I've just push new maui-manager-git to AUR and add it to depends list in this commit, You can test it and hopefully no more error.

The installation fails since the update to version v0.5.0.r26...

it seems that you need the maui-manager package to compile the maui-shell. The problem is that maui-manager is not yet available in AUR for the x86-64 architecture.

@luntik2012 it's seem you have --noconfirm parameter when use pacman/yay/paru/etc. so it don't prompt you a confirmation when it's try to replace mauikit with mauikit-git and decide it to abort automatically. you should remove that option parameter or add this --confirm parameter as well to override previous parameter

--noconfirm
    Bypass any and all “Are you sure?” messages. It’s not a good idea to do this unless you want to run pacman from a script.
--confirm
    Cancels the effects of a previous --noconfirm.

pacman(8) Options

:: Checking for conflicts...
:: Checking for inner conflicts...
 -> Inner conflicts found:
 -> mauikit-git: mauikit
 -> package conflicts can not be resolved with noconfirm, aborting